Trust and security
Security & Trust
FactoryOS sits between your engineers and the agents writing your code, so it has to be the most careful system in the room. These are the controls, where your data lives, and who else handles it.
Agents stay inside the lines you draw
The controls that decide what an agent may do, and what always needs a person.
No silent merges
Agents open pull requests; engineers merge. Always. The platform has no mechanism to auto-merge code.
Policy at every gate
Gates are evaluated by Open Policy Agent. Every gate starts required, and relaxing one needs a second security admin and produces an audit event.
Sandboxed agent runs
Coding agents work in a sandbox with scoped repository credentials and a budget cap that stops a run before it overspends.
Your data is isolated and protected
How tenants are kept apart, and how secrets and credentials are handled.
Tenant isolation
Every query filters by tenant, and row-level security is enforced in Postgres across the identity, tenancy, integration, policy, intelligence, cost, audit and registry planes.
Secrets in Vault
A model key you connect is held per tenant in HashiCorp Vault, never in our database and never shown again once saved.
Encrypted in transit and at rest
Traffic to FactoryOS is encrypted with TLS, and platform data sits on encrypted storage.
Managed identity
Authentication is handled by a dedicated identity provider, so FactoryOS never stores your passwords. Single sign-on is supported; talk to us about SCIM provisioning.
Everything is on the record
What you can show an auditor, and what we will and will not do with your data.
Append-only audit log
Every state-changing action produces an audit event. The log is append-only, hash-chained per tenant and tamper-evident.
No training on your data
We do not use your data to train models.
SOC 2 Type I in progress
We are working towards SOC 2 Type I, monitored continuously with Vanta. It is in progress, not achieved.
Where your data lives
Hosted in Australia during the beta
FactoryOS runs on Oracle Cloud Infrastructure in Sydney, Australia. We plan to move hosting to AWS once FactoryOS is generally available, and will give notice before we do.
If you connect your own model provider key, that provider processes the requests made with it under your own agreement with them.
Sub-processors
| Provider | Purpose | Location |
|---|---|---|
| Oracle Cloud Infrastructure | Hosting: application, database and secrets store | Sydney, Australia |
| Anthropic | Model inference for the platform default, through our LLM gateway | United States |
| Voyage AI | Text embeddings for search over your decisions and documents | United States |
| Stytch | Identity and authentication | United States |
| Resend | Transactional email, such as sign-in codes and notifications | United States |
The same list is part of our DPA.
Responsible Disclosure
If you discover a security vulnerability in FactoryOS, please report it to security@agentfactoryos.com.au rather than opening a public issue. We aim to respond within 24 hours and will keep you informed as we address the issue.