Owner
- Sees
- Every system of the software house, the team, the logs.
- Can
- Invite and remove people, grant and revoke keys, authorize production keys, block or release emergency keys.
Symbiont describes your clients' systems and keeps access in order, but it does not store passwords or keys: these are held in the vault, the encrypted store of keys. This page explains where each piece of data is kept, who can do what, and what remains your responsibility. It is intended for those who run a software house and for those who, on the client's side, need to assess whether the service can be trusted.
dbc, Symbiont's program for the terminal, which the app installs on the computer and which the coding assistant uses to describe systems and handle keys.[secret:NAME]. When a command needs the key, dbc retrieves it from the vault and passes it directly to that command: the assistant never receives it..env and other files with keys, printing environment variables, or querying the vault or the keychain.It should be noted that the guard is a barrier against mistakes, not a guarantee. A program running under your user account can find another way. For this reason, values are read only inside dbc, never in files that the assistant can open.
Each software house sees only its own data: the rules are defined in the database, row by row, and are verified by automated tests. For people working in the software house, they apply only after authentication with the second factor.
For clients the second factor is optional; once turned on, it is required at every sign-in. Platform administrators are required to use it, as owners are.
Some systems have only a production environment, and during an incident the keys are needed there. Instead of copying them by hand, without any record, an official procedure with dedicated protections is available.
It never runs together with the restoration of development keys. A window first shows the exact names and the file; the operation is then confirmed by fingerprint. It is reserved for owners and for members whom an owner has authorized for that system: the server verifies this every time.
One file per environment, readable only by the computer's user and written only if git excludes it. A different value already present is not replaced without confirmation. The coding assistant does not read it.
The system's log records who retrieved the keys, on which computer, and which keys (names only). After 7 days the app reminds the user to remove them; removal takes one click.
continuity.yaml, a text file kept in the client's repository, readable without Symbiont.The session is stored encrypted with the operating system's keychain; where no keychain is available, as on Linux without a keyring, the app stores neither the session nor the local copy. The vault's master password never passes through the app.
To allow work without a connection, the app keeps a copy of systems, maps and procedures. Every row is encrypted (AES-256-GCM) with a random key protected by the operating system's keychain. The copy never contains key values or vault contents.
The copy is erased at sign-out, when the user is no longer part of the software house, or when another person signs in. Sensitive operations, such as releasing keys, removing a person or revoking a computer, require fingerprint confirmation (Touch ID) on a Mac.
| Service | Provider and location |
|---|---|
| Database and sign-in | Supabase · EU (Frankfurt) |
| Web app and vault | Hetzner · Germany (Nuremberg) and Finland (Helsinki) |
| Backups | Hetzner · Germany; second copy on Cloudflare R2 · EU |
| Account emails | Resend · sent from the EU (Ireland) |
| Payments | Stripe · EU (Ireland) |
The full list of providers and the security measures are in the privacy policy and the data processing terms.
If the software house uses Bitwarden cloud or its own vault, the security and backups of that vault remain its responsibility, and automatic releases and revocations do not apply: they remain manual steps.
Security problems should be reported to security@getsymbiont.com, with a description of what was found and how to reproduce it. Please do not use other people's data and do not make the problem public before it has been fixed. If a breach concerns the personal data that your software house processes with Symbiont, we will inform you without undue delay, within 48 hours of becoming aware of it.