Your files never leave your cloud.
Filebot Enterprise runs the processing inside your own infrastructure. Files stay in your buckets, keys stay with you, and our control plane only ever sees metadata, never file contents.
Full custody
Files live in your buckets and are processed on machines you run. There is nothing to hand over.
Compliance, covered
Data residency in your region, SSO and SAML sign-in, and an exportable audit log of every action.
DPA with SCCs + UK IDTA · 72 h breach notice
Nothing taken on trust
The control plane schedules work and passes references. It never reads file bytes, and handoffs are signed by your own agents.
Three steps to bring it inside.
Your platform team runs a small service. Filebot does the orchestration.
Run the agent
Deploy the Filebot agent in your VPC. It is a small service that registers with your organization and forms your processing pool.
Connect storage and keys
Point agents at your buckets. Credentials sit in an encrypted vault, or stay only inside your environment.
Files flow, bytes stay
Every run routes steps to your agents. Filebot sends instructions and receives status, and your files never cross the boundary.
The whole install.
One container, any cloud. Point it at your control plane, hand it a one-time token from the dashboard, and it joins your pool.
$ docker run -d \ -e FILEROBOT_URL=https://api.filebot.dev \ -e FILEROBOT_AGENT_TOKEN=fr_agent_… \ <agent image, from your dashboard>Run a pool of agents.
Agents register per organization and form your pool. For each step, Filebot picks the agent with the fewest runs in flight, from the ones online, capable, and allowed to run it.
- Routes to the least-busy agent in the pool
- Online status comes from agent heartbeats
- Matches on capability and provider
- Honors strict-privacy support
The next step routes to agent-cpu-2, the idlest online agent able to run it.
Zero egress, strict privacy.
Set a privacy mode per pipeline. In strict mode, intermediate files stay in your workspace bucket and the control plane never reads object bytes. The agent signs the short-lived handoff URLs between steps and the final delivery URL.
- Standard or strict privacy mode
- Strict keeps intermediate files in your workspace bucket
- The control plane never reads object bytes
- Your buckets on S3, R2, or S3-compatible storage
- Your credentials in an encrypted vault
Object bytes never cross the boundary. Filebot orchestrates by reference.
Security and trust.
The controls behind zero-knowledge processing, end to end.
Signed cross-agent handoffs
Handoffs between agents and the final delivery use short-lived signed URLs.
Encrypted credential vault
Your storage credentials sit encrypted at rest with AES-GCM.
SSRF guards
Filebot checks imports and webhook targets to block requests to internal addresses.
Signed webhooks
Filebot signs every webhook delivery. You verify it came from us.
Organization roles
Owner, admin, and member roles scope what each teammate does.
Audit log
Filebot records member and API-key changes for review.
Bring file processing into your cloud.
Talk to us about running Filebot agents in your environment.