The whole platform, open source.

An agent platform is trusted with a lot. It holds your code and the keys to your services, it signs in to your people’s AI plans, and it runs commands on computers in your account all day. Before a company lets one in, somebody has to answer three questions: what does it create, what does it send out, and who can reach what. With closed software the answers come from a questionnaire and a promise. With the source, your team checks.

Here each one can be checked. The installer is one file of plain JavaScript, and its plan mode lists every app, disk, bucket, address, certificate, token and secret it would make, with Fly’s price for each, before it changes anything. The daily report your Agentic Cloud sends us is counted in one file, copy-pulse-facts.ts: counts and the contact you chose, no messages and no code, and your admin sees every report and can turn it off. How a saved key is encrypted and handed to an agent’s computer is in the open too. You do not have to take our word for any sentence on this site.

The AGPL-3.0 is a copyleft licence: it lets you use the platform, read it, run it, change it and share it. Its one demand beyond the ordinary GPL is about networks. If you run a modified version as a service, you must offer its source to the people who use it. That closes the gap the ordinary GPL leaves for software people use over a network rather than receive as a copy.

It also means a team that wants a workplace for agents of its own making can start from this one rather than from nothing, on the same terms. The licence covers the code. Your lawyers will want to read the licence itself, and it is one file at the top of the repository.

Some products open a client or a software kit and keep the service behind it closed. This repository is the whole platform, the parts that run your agents included. Here is where each part lives.

Start with the README. It sets out the product’s shape, what happens during one turn of an agent, and how data is split between your side and the control plane. Then follow the question you care about. For what lands in your cloud, read infra/copy-installer and public/own-cloud.md, the guide an agent follows to install it. For what an agent can ask the Workspace to do, read cli/agentbuilt and the routes behind it in backend/src/routes. For why things are the way they are, docs keeps the runbooks and dated design records.

Or hand the reading to an agent. Clone the repository, open Claude Code or Codex in it, and ask what it sends outside your account, or what an agent can do without a person’s yes. It is a large codebase, and that is a fast first review whose answers point to files you can check yourself.

The repository’s page shows the code, every commit and every proposal, with no sign-in, and gives the address to clone it with git.

The platform is built on the platform. Every change arrives as a proposal on its own git host, runs its checks, and lands by the owner’s yes, or by itself once the owner has turned on auto-merge. Almost every commit in its history is signed by an agent, by name. If you want to see how a team of agents works on real code, the history is a record of exactly that.

It does not mean it installs anywhere: the installer builds your own Agentic Cloud on Fly, and why it runs on Fly is its own page. You can read the code and run it locally for development, as the README shows, but the one supported way to run it for a team is the installer.

It does not mean we take changes from anyone. The git host takes no proposals from outside, so write to the founder before you start. An outside change needs a contributor agreement, which lets the copyright holder keep the right to offer the project under other terms later, while what you contributed stays available under the AGPL-3.0.