Product guide / Artifacts
the work you keep, with its sources
Keep the work and its sources.
Artifacts turn a useful result into a durable, versioned object with its provenance intact — reusable long after the conversation that produced it.
Mermaid artifact
Nexus Analytics client acquisition strategy
Where this helps
Analysis that cannot be traced back to its sources has to be redone before it can be reused — and it is always needed under time pressure.
The question it puts in front of you
Is this result worth keeping, and can we show where it came from?
Where judgment belongs
You decide what gets finalized, forked, placed in a Room, or archived.
What gets prepared for you
Provenance, versions, and format-specific rendering are preserved without anyone remembering to ask.
Structured work
What survives the conversation.
Keep documents, diagrams, structured data, and generated files in one company library.
Inspect sources, citations, confidence, and version history where available.
Move, copy, fork, discuss, finalize, archive, or place work in a Room.
Use format-specific viewers instead of flattening every output into a document.
Artifacts in the real world
The output that outlives the thread.
An Artifact moves through draft, final, and archived, and restoring one brings it back to draft. AI revisions create versions you can browse; ordinary editing saves in place. Putting one in a Room adds a second access boundary without changing the object itself.
Supported formats include plain text, Markdown, Mermaid, JSON, CSV, XLSX, YAML, TOML, XML, HTML, SVG, React components, and JSON-render content.
What holds up
What it does well, and what it was never meant to do.
Constraints are a design position, not an apology. Everything on the left ships today; everything on the right we decided against.
What you can rely on in Artifacts
- Download directly from the editor, in the format the Artifact is in.
- Branded PDF where the format supports it.
- Takes output from Chat, Genesis, Intelligence, Reports, and Rooms alike.
What we chose not to build
- Not every manual edit creates a new version — autosave updates in place.
- Controls differ by format; there is no single universal toolbar.
- Not every Artifact type can be made public.
Outputs & automation
Native download for supported Artifact formats · Branded PDF where the Artifact renderer supports it
None of this is trapped in the interface. The same API and CLI that produce these outputs are how you drive Operalta from your own tools — a script, a terminal, or another product entirely.
Works with
Where Artifacts hands the work on.
Decisions rarely stop where a product does. These are the guides that pick the work up next.
For your company
See how Operalta fits your company.
Bring one current decision or process. We will map it together.