Deploy

These pages show how to run Kindgi in your own infrastructure, next to your data, and how to operate it there. Kindgi is self-host first: the runtime you run on your machine with kindgi dev is the same image you deploy. Your pack's code runs beside it, in a pack service built from your app.

Access to the runtime image

Sign in at access.kindgi.com with GitHub for the runtime image's pull credentials, and log in once with kindgi auth registry (see Install). Questions or trouble: contact@kindgi.com.

• Self-host with Docker: the runtime and your pack service as containers, with your own Postgres.
• Operate it: health and logs, backups and restores, upgrades, and rotating its tokens and keys.
• Serve many tenants: one runtime for tenants who don't trust one another: the settings it starts only with, the operator's system keys, a pack service for each deployment, and closing and purging a tenant.
• Keep secrets in your own secret manager: Azure Key Vault, Google Secret Manager or HashiCorp Vault holds the secrets set through Kindgi's API, and Kindgi keeps their names and versions.
• Keep and purge deleted data: how long deleted records are kept, and the retention policies and sweeps that purge them.
• Run with authorization: what it gives and what it doesn't, and running OpenFGA next to the runtime.
• People, API keys and service accounts: add people and give them roles and their own keys, give pipelines service accounts, and remove someone in one step.
• Turn on sign-in: people sign in to the console with their organization's identity provider, Google, Microsoft or GitHub, or a link by email.
• Google Cloud Run: the runtime and your pack's service as two Cloud Run services, with Cloud SQL, from Kindgi's Terraform module.
• Azure Container Apps: the runtime and your pack's service as two container apps, with PostgreSQL Flexible Server and Key Vault, from Kindgi's Terraform module.
• Kindgi Cloud: we run it for you. In private preview.