Last updated 20 October 2026

Security and data handling

How a Manufactoria installation is set up today. Your pilot agreement is the binding version.

Your own installation

We run Manufactoria for you. Each customer gets an installation of its own: its own engine, database, storage and private network. Installations run side by side on servers we operate. They don't share databases or storage.

An installation has no open ports. It is reached through an encrypted tunnel, behind an access check that admits only the people on your installation and our operators.

Signing in

• Passwords are at least 10 characters and are stored only as argon2id hashes.
• Each account can turn on one-time codes from an authenticator app, with 8 recovery codes.
• 10 wrong passwords or codes within 15 minutes lock the account for a while, even against the right password.
• A session lasts 12 hours by default and is renewed while you work. Every session ends 7 days after sign-in.
• Accounts are owners, admins, members or viewers. Only owners and admins can connect repositories or change model keys.

Who can change your code

• The developer works in its own copy of the repository, on its own branch.
• The planner, reviewer and QA get a read-only copy pinned to one commit, with pushing switched off. If one of them edits a file, its step fails.
• The engine, not an agent, pushes the task branch and opens the pull request.
• Nothing merges unless you merge it, or you switch on auto merge for an installation or project.

Before an agent runs a shell command, the engine checks it against rules: no merging, no pushes to protected branches, no history rewrites, no changes to git settings or remotes. A refused command is recorded on the task. These rules stop mistakes. They are not a sandbox, so the next section matters.

Credentials

Manufactoria reaches GitHub with a token you give it for each project. The engine hands the token to git privately, never in a command line or a web address. Model keys, when you bring your own, are saved once per provider, never shown again after saving, and kept out of task records and logs.

Agents run inside your installation, so give the token only the access Manufactoria needs. We recommend a separate machine account that can see only the repositories you want worked on.

Where your code goes

Agents read your repository to do the work. The model provider behind each role receives the task, the files an agent opens, the changes it makes and the output of the commands it runs.

If you use your own model subscription or key, this happens under your agreement with that provider. If you use Manufactoria credits, the pilot agreement names the providers.

What we keep

• Working copies are deleted 7 days after a task finishes. Each project can change this.
• Task records stay for the life of the installation: the definition of done, the plan, reviews, checks and decisions. They are the record you get back.
• Sign-ins and admin actions go to an append-only audit log.
• When an installation is closed, we delete its database, files and network setup. The agreement says when that happens and how long we keep a final export.

Report a problem

If you find a security problem, write to contact@manufactoria.ai. Please give us time to fix it before you publish.