Digital business continuity

AI lets small studios build big systems. Symbiont makes them last.

Continuity for software and infrastructure built and run by small studios and freelancers. Systems are documented while they are built, every key stays in the client's own vault, and emergency access is tested before anyone needs it.

Request early access Watch the demo · 8 min
Big systems, small studios Documented while they are built Emergency access that works Vetted stand-in freelancers
The problem

If the studio is gone tomorrow, who takes over?

With AI, a team of two can build a SaaS platform, a CRM or the integrations a company runs on. That's a real saving for the client. But the more important the system, the more one question matters, and today the honest answer is often “nobody could”.

The domain is registered to the developer's personal emailacmelogistics.it
The code sits in a personal accountgithub.com/luca-ferri/acme-tms
The only SSH key is on one laptopapi.acmelogistics.it
The database password lives in a local file.env on the developer's machine
And with NIS2 it's no longer just a risk. Companies in scope must manage the security of their suppliers. A small studio that can't prove continuity risks being left out of exactly the projects it can now build.
The answer

A small studio, as dependable as a large one.

1 · WHILE YOU BUILD

Documented as it's built

Claude Code skills keep continuity.yaml true in the client's repo: components, environments, hosting, deploy, access and backups.

available
2 · THE CONSOLE

The map is already drawn

Systems arrive on their own. The consultant reviews and confirms; the client confirms the few facts only they know, from a link.

private preview
3 · THE VAULT

Keys in the client's vault

Every secret goes from where it's born straight to the client's Bitwarden. The AI only ever sees a reference. Emergency access is generated and tested.

available
4 · THE NETWORK

Vetted stand-ins, ready

Freelancers already under contract, who get access only on activation, after a waiting period, if the studio can't answer.

in design

While developing

With the continuity skills on, every new database, server or token updates the description and lands in the vault. dbc manifest push sends the description, never a secret, to the platform.

Systems built before

A read-only audit agent runs once and pre-fills the same data. The AI then asks only what's missing, in context.

Rules decide, not the AI

Deterministic, tested rules compute the traffic light, the requirements per tier, NIS2 and a report branded for the studio. The AI gathers facts; it never picks a colour.

NIS2

Evidence about suppliers, without the enterprise price.

For clients that are essential or important entities, Symbiont turns on ten requirements linked to Article 21(2) and adds an “NIS2 evidence” section to the report. It's evidence, not a certification.

For the studio

  • Proof it can win and keep NIS2 clients
  • Continuity documented as a by-product of normal work
  • A report in its own name, ready for the client's audit

For the client

  • Owns every account, every key and the code
  • Emergency access that has actually been tested
  • Evidence on its suppliers for its own compliance
Demo

See it end to end, in eight minutes.

Product demo. Everything shown is fictional: the studio, the client, hosts and data.

Principles

Built so it outlives any vendor, including us.

  • The client owns everything: accounts, code, vault.
  • The AI gathers; deterministic rules judge.
  • Secrets never pass through the AI or the platform. Only references do.
  • Every fact has a provenance: declared, discovered, confirmed by the client, verified.
  • Plain text in the client's repo. continuity.yaml is readable without us.
  • EU first: data hosted in the EU, vaults on Bitwarden EU.

Build big. Make it last.

We're onboarding a first group of studios and their clients. Tell us what you build and for whom.

hello@getsymbiont.com