Data residency for AI coding agents.

In the hybrid shape the agents already work inside your network. Ticinuum lets you decide what its own storage keeps — per family of artifact, from three presets — and point your run artifacts at your own S3-compatible bucket. We won't write "your source never leaves your network"; here is the matrix instead.

Early access ↓

Data residency & bring your own bucket

Choose what lands where.

The hybrid shape already runs the agents inside your network. Now you decide which artifacts Ticinuum stores at all — per family, with three presets — and whether your run artifacts land in your own S3-compatible bucket instead of ours.

Three presets, one switch each — Standard keeps everything on the platform (the default). Restricted stops workspace snapshots, diffs, the repo-survey cache, and webhook archives. Minimal adds rendered prompts, the run-log archive, the test and other reports an executor produces, workstation-attached artifacts, and finding evidence — every family that can be turned off. An advanced per-family matrix sits behind the presets.
Off means never produced, not deleted later — a disabled family is refused at the gateway with a machine-readable reason, and the executor is told the policy at run start so it never builds the tarball or captures the diff at all — nothing crosses the wire. If the policy cannot be resolved, the write is denied.
Bring your own bucket — point run artifacts, run-log archives, repo surveys, uploaded attachments, and webhook archives at your own S3-compatible bucket. The control plane signs each upload against your endpoint and the executor still holds no storage credential. Grant a read-only key and the app renders diffs and plans from your bucket through short-lived links; withhold it and you see references only.
The cost is disclosed before you choose — every off switch shows what stops working and what still works before it accepts the change, warns that turning a family back on never recovers what was never produced, and months later the empty panel says "your organization chose not to store this" — with who and when — instead of looking like a broken agent.

Honesty note: by default artifacts still land in Ticinuum's storage — a snapshot of the working tree (git history excluded), diffs, plans, rendered prompts, summaries, run-log archives, and repo surveys. Under Minimal without your own bucket, a paused run's conversation state, plans, summaries, and uploaded attachments still do; artifacts attached from a workstation over MCP land with us unless that family is off. Your own bucket is S3-compatible only, all-or-nothing per org, verified at the storage layer against MinIO — not yet end-to-end or against AWS — and while it is on, a child agent cannot read its parent's plan. The control plane holds your write credential encrypted to sign uploads. Every change is audited per family.

In the product

Captured from the product.

Real screens from Ticinuum’s own organization, taken in October 2026 — not mockups.

The Data residency settings page: Standard, Restricted and Minimal presets with the active one marked, a warning that the change is not reversible for past runs, and sections for the advanced matrix and your own storage bucket. — **Settings · Data residency** — Three presets for what Ticinuum’s storage may keep, with a warning that turning a family back on never recovers what was never stored.

Roadmap fence

Data residency: what's opt‑in, and what isn't built.

What's built but off until you turn it on, and what isn't built yet. Open any row for the whole sentence, or read the whole fence.

On the roadmap Not built yet, or built but not yet validated in use. Don't rely on these. 2 items

DataBring-your-own-bucket, finished — per-family routing (today it is all-or-nothing per org), GCS / Azure, and end-to-end + AWS conformance
DataOpt-in prompt-content ingestion — an undecided governance question; today prompt content is never captured

FAQ

Questions, answered plainly.

Does our source code reach Ticinuum?

In the hybrid shape the agent clones and works inside your network, and your model provider sees what any coding agent sends it. What Ticinuum itself stores is a policy you set. By default its storage holds a snapshot of the agent's working tree (never the git history), diffs, plans, rendered prompts, summaries, run-log archives, and repo surveys. The Restricted preset stops the snapshot, diffs, repo surveys, and webhook archives; Minimal adds rendered prompts, the run-log archive, the test and other reports an executor produces, workstation-attached artifacts, and finding evidence. Even then a paused run's conversation state, plans, summaries, and uploaded attachments still land with us — unless you point your run artifacts at your own bucket. Ticket text, events, cost, and audit rows always live in the control plane. We won't write "your source never leaves your network": it isn't true of any hosted control plane, and we'd rather show you the matrix.

Can we use our own bucket?

Yes — any S3-compatible bucket. An org admin adds an endpoint, a bucket, and a write credential; Ticinuum verifies it with a round trip (screened so it can't be pointed at internal or cloud-metadata addresses) before using it. From then on run artifacts, run-log archives, repo surveys, uploaded attachments, and webhook archives are written to and read from your storage; the control plane signs each upload against your endpoint and the executor still holds no storage credential. Add a read-only key and the app renders diffs and plans through short-lived links; skip it and you see references only, with the offer to add one. Said plainly: it is all-or-nothing per org, the control plane holds your write credential encrypted in order to sign uploads, artifacts written before you switched stay where they were, artifacts attached from a workstation over MCP still land with us unless that family is off, planner decomposition is degraded until one read path is converted, and it is verified at the storage layer against MinIO — not yet end-to-end or against AWS.

The rest of the deep dive

Every other guardrail, on its own page.

Put your backlog on the continuum.

From intent to PR to review — one durable, auditable continuum of work. Early access opens soon.

coming soon

Early access opens once the waitlist terms and privacy notice are final. Nothing to sign up for yet — this page collects no email.