What's next?

Available

Deployed and supported. The fields and commands described here are stable within version v1alpha1.

Your first application is running. Here is where to go next depending on what you want to do.

I want to deploy a real application

• You already have a docker-compose.yml: From docker compose.
• A database, migrations, scheduled tasks: Services, jobs and cronjobs and Storage.
• Passwords and API keys: Secrets: create and read, then Injection into an App.
• Scaling, health probes, zero-downtime updates: Healthchecks and scaling.

I want my own domain name

Bring a domain, then Domains on an App.

I want to deploy from my CI

• Without a secret, with OIDC: your GitLab or GitHub pipeline obtains a tenant session without any stored token.
• Complete examples: GitLab CI, GitHub Actions.
• Build and push your images: Images from CI.

I want to host my images

Image registry: one private repository per application, access keys for your applications and your CI, a retention policy.

I want to know if it works

Monitoring: HTTP, TCP or DNS probes, alerts to Slack or a webhook, and a public status page.

I want to give my team access

Identity and access: policies, roles, read-only access, machine accounts.

I want to version everything in git

The validate, plan, apply cycle and Environments and restore: sng pull exports the desired state, sng plan compares, and sng env freezes what is running or returns to a previous version.

I want to know what the platform guarantees

Security and privacy: isolation, protection by default, secrets, access.