trevato/open-platform
Public: anyone can read this; nobody can change it.
Open Platform: one platform for an organization's internal applications. Open source under AGPL-3.0.
Something wrong? Report a problem, no account needed.
This repository has no app yet.
- .claude
- .forgejo
- bin
- deploy
- docs
- genesis
- recipe
- scripts
- wiki
- .gitignore 449 B · ~129 tok
- CONTRIBUTING.md 559 B · ~140 tok
- flake.lock 1.9 KB · ~663 tok
- flake.nix 4.9 KB · ~1.4k tok
- green 0 B · ~0 tok
- LICENSE 33.7 KB · ~9.9k tok
- NOTICE 353 B · ~101 tok
- ORIGIN 228 B · ~66 tok
- README.md 3.5 KB · ~885 tok
README.md
Open Platform
Open Platform is a platform for an organization's internal applications. Users submit requests from inside an application. Developers and an AI build agent implement each request in a pull request with a preview environment, and the change is reviewed, merged and deployed on the organization's own infrastructure.
Every application starts from a shared application template that provides authentication, data access, configuration, metrics and tests, so application code is mostly business logic. Rules that stop changing become reviewed configuration. Each infrastructure layer has a default component, built-in options and integration options, listed in the bill of materials. EspoDev deploys, integrates and supports Open Platform.
Components
Open Platform has two components:
- The platform is what an organization deploys: the shared application template,
application hosting, code review, deployment and administration on Kubernetes. This repository contains the platform.
- The forge is a single-user workspace: git hosting, issues, pull requests, preview
environments and an AI build agent in one program. A developer can pull an organization's code into a forge, work on it there, and open a pull request to the organization's repository.
The forge runs the complete request workflow, from the request inside the application to the status update back to the user. A platform deployment runs the workflow from the issue on: issue, AI build agent, pull request, preview, review, merge and GitOps deployment. Who may merge a change from the AI build agent is a configuration setting.
Set up a forge
See the forge repository and follow its README. The forge requires Bun, not this repository.
Deploy the platform
The AI build agent reads its AI model provider credential from CLAUDE_CODE_OAUTH_TOKEN
(subscription) or ANTHROPIC_API_KEY (API billing).
git clone https://forge.open-platform.sh/trevato/open-platform.git && cd open-platform
CLAUDE_CODE_OAUTH_TOKEN=<your-token> nix run .#up
The first run builds from source and takes 30 to 60 minutes. Linux is the tested host operating system.
Requirements:
- Nix with flakes
- Docker with about 4 CPUs and 10 GB of memory
- Ports 80 and 443 free, or
HTTP_PORTandHTTPS_PORTset - A credential from your AI model provider, set as shown above; without it the AI build agent
stays idle
The install prints the location of a generated age key. That key decrypts every secret on
the platform, so store a backup offline. To deploy on AWS, Azure or DigitalOcean, see
deploy/.
Further reading
- Requirements and compatibility: what each deployment requires, and the
default, built-in options and integration options for each layer
- Platform guide: installation stages, use and operation
- Wiki: the user and operator guide that ships with each platform
- Architecture,
bill of materials, MCP, security, leadership brief
Open source under the AGPL-3.0. See contributing.