Astrolift¶
Astrolift is an opinionated, multi-tenant, multi-cloud Platform-as-a-Service. It lets engineering teams onboard a Git repo, declare requirements via a single astrolift.toml manifest, and deploy onto any Kubernetes cluster -- vanilla, EKS, GKE, or AKS -- with the same control plane.
What you get¶
- One manifest, any cloud. Define your app's shape once. The platform handles the rest.
- Managed services on demand. Declare a Postgres database, a Redis cache, or an object store in your manifest. The platform provisions it.
- Preview environments. Every pull request on a preview-enabled app gets an isolated environment with its own URL.
- Zero-downtime deploys. Rolling updates, health checks, and rollback to the previous deployment's exact image out of the box.
- Agents and workflows. Register agent manifests from the same repositories, dispatch them as bounded Kubernetes Jobs, chain them with workflow TOML, and answer their questions from your inbox.
- Multi-tenant by design. Organizations, teams, projects, and fine-grained RBAC from day one.
Next steps¶
App developers¶
- Getting Started -- install the CLI and deploy your first app.
- Choose a client -- use the dashboard, CLI, GraphQL API, or MCP.
astrolift.tomlreference -- current manifest fields and recipes.- Agent packages -- compose prompts, skills, tools, files, and monorepos.
- Using the dashboard -- a tour of the web UI.
- Working with apps -- registering, deploying, manifest sync, secrets, sub-resources, temporary apps.
- Running an org -- access, infrastructure, governance, platform signals.
Platform operators¶
- For Operators -- what an Astrolift install looks like, install paths per cloud.
- Installing Astrolift -- pick a cloud, follow the runbook.
Reference¶
- Platform reference -- the index of client contracts and how they are versioned.
- CLI · API · MCP -- the three programmatic clients.
astrolift.toml· Workflow TOML · Agent packages -- the declarative formats.
Documentation for tools and agents¶
All reference pages are plain Markdown. AI clients can start at
/llms.txt, and the astro binary can print or export its
release-matched documentation without a browser. See the
CLI reference.