FAQ
Questions we hear most
01The platform
Deployments.ai is an agent platform you embed in your product. You define agents as code, publish them as immutable releases, deploy them per environment, and run them through one thread and run model — with the model gateway, tools, sandboxes, memory, channels, agent email, workflows, streaming, observability, usage, and governance already built in.
A framework is a library you call from your own code. Deployments.ai is the platform underneath: the control plane, the hosted runtime, the secrets vault, the tool and channel integrations, and the operational pipeline. You can still bring your own logic through tools, MCP servers, HTTP callbacks, and client-executed tools.
Agents call models through a private gateway with OpenAI, OpenRouter, and Amazon Bedrock as providers. Each environment has a model policy that decides which models are allowed, and agents can declare fallback models. Provider keys stay in the gateway.
The catalog includes more than 170 integration providers, among them 130+ vendor-hosted MCP servers such as GitHub, Notion, Linear, Sentry, Google Drive, Jira, and Zendesk. You can also add your own MCP servers, HTTP callbacks, hosted functions, and tools that run inside your own application. See tools and integrations.
02Source and license
In the Agentifiers/deployments repository on GitHub: the control plane and public contract, the agent runtime, tools and channels, the operational pipeline, the OpenTofu modules and deploy tool that install it, and the CLI and SDK. See what's in it.
The platform is licensed under the Functional Source License, Version 1.1, with the Apache License 2.0 as its future license (FSL-1.1-ALv2). FSL is a Fair Source license, not an OSI-approved one: the source is public, with one restriction on competing use. Each release becomes available under Apache 2.0 two years after it is published. The TypeScript SDK and the deployments CLI are MIT licensed.
You can read the code, self-host it, and modify it for your own use, including commercial use inside your business. You cannot offer it to others as a competing commercial product or service. White-labeling or reselling the platform to other companies is a competing use and needs a commercial license from Agentifiers; talk to us. If you are unsure whether your use competes, ask us first.
Agentifiers. The same team also helps companies set the platform up in their own AWS accounts, and offers it hosted and managed.
03Running it
Yes. You bootstrap an AWS account once, then the deploy tool applies the platform's OpenTofu root and ships its images and functions into that account. Each installation runs in one dedicated AWS account and region. You can run it yourself from the source, or have Agentifiers set it up for you in an AWS account in your AWS Organization.
Yes — Agentifiers offers the platform hosted and managed, with the same platform and API as the self-hosted version. Request access.
AWS building blocks: Lambda, ECS on Fargate, DynamoDB, S3, KMS, EventBridge, Kinesis, SQS, API Gateway, OpenSearch, and SES, among others. There is no Postgres in the target architecture.
Self-hosting is free under the license; you pay your own cloud and model costs. Pricing for setup and hosted access isn't published yet — talk to us.
04Security & data
No. Credentials live in a KMS-encrypted vault and are injected only at execution. They never appear in manifests, OpenTofu configuration, tool calls, messages, artifacts, or the thread stream.
Yes. Organizations can set retention, run a full tenant export, request erasure, and create signed audit exports that auditors can verify independently.
Not today. Deployments.ai is pre-release. We publish the controls the platform implements on our security page rather than claiming certifications we don't have.