Forge

Forge takes a Git repo and runs it at a public URL. You push a release; Forge reviews the commit, builds a container, and serves it at https://<your-app>.apps.sandbox.mithran.cloud. You don't provision servers or manage deploy keys to make that happen.

The whole loop is five steps, and you only do the first four once:

1. Install the aegis CLI.
2. Sign in.
3. Connect your GitHub account (install the Forge GitHub App).
4. Onboard a repo with one command. It adds a mithran.yaml, drops in a deploy workflow, and registers the repo with the control plane.
5. Push a release/** branch or a vX.Y.Z tag. That's the deploy.

After onboarding, shipping is just git push. The deploy runs on a GitHub-hosted runner, authenticates to Forge with a short-lived GitHub OIDC token (no stored secret), and the control plane does the rest.

Start here

• New to Forge? The Quickstart gets a repo to a live URL in about ten minutes.
• Already onboarded and just want to ship? See Deploy.
• Something broke? Troubleshooting covers the failures people actually hit.

What you need

• A GitHub account (personal or org) where you can install a GitHub App.
• A repo with an HTTP app that listens on the port in $PORT and answers GET /health with a 200.
• A Mac to run the CLI. The deploy itself runs in GitHub Actions, so your laptop doesn't need Docker.

Forge is in preview

The serving model, the URLs, and the commands here are real and live in the sandbox environment.