What's new in Suga

When creating a new environment, you can now fork variables from an existing one. Instead of re-entering every variable from scratch, select a source environment and its variables will be carried over.

A review step shows exactly which variables will be copied before anything is applied, so you can adjust values (like swapping production URLs for staging ones) before confirming. This is especially useful when spinning up preview or staging environments that share most of their configuration with production.

Switched environment variable masking from native input type toggling to CSS-based masking. This fixes cross-browser inconsistencies where some browsers would offer to save masked values as passwords or interfere with copy/paste behavior.

Navigation has been overhauled with a new app sidebar that works at both the org and project level. Org settings like billing, members, cluster configuration, and variables are now accessible directly from the sidebar instead of through nested settings pages.

The sidebar adapts based on context: at the org level it shows org-wide settings and navigation, and within a project it switches to project-specific links. A collapsible mode toggle lets you minimize it when you need more canvas space. Mobile users get a dedicated trigger for the sidebar as well.

Several improvements to the GitHub integration experience:

• Permission updates are handled gracefully without losing auth state
• Git connection cards in the build config show the connected repo clearly
• GitHub repo names are used as display names for cleaner service labels
• Consistent header sizing on the GitHub settings page

Environment variable references are now checked for circular dependencies. If service A references a variable from service B, which references one from service A, you'll see a clear warning on the canvas before deploying. Circular edges are rendered with a distinct style so they're easy to spot.

Circular references cause infinite resolution loops at deploy time, which previously resulted in confusing deployment failures. Now these are caught before you deploy.

Services will now automatically rebuild and update when you `git push` to your repository.

What is Keel#

Keel is a Kubernetes operator that watches for new container image tags and triggers rolling updates automatically. It runs inside your cluster and listens for webhook notifications from container registries (Docker Hub, GitHub Container Registry, etc.).

When a new image tag is published, Keel receives the webhook, matches it against your deployment's image policy, and initiates a rolling update. No CI/CD pipeline changes needed.

How it works in Suga#

When you deploy a service through Suga, we configure Keel's image update policy for that deployment. Push a new tag to your registry, and Keel handles the rest: it detects the new tag, updates the deployment spec, and Kubernetes rolls out the new pods.

This is particularly useful for teams that build images in external CI systems (GitHub Actions, CircleCI, etc.) and want deployments to update automatically without triggering a full redeploy through the Suga dashboard.

New organizations now get build infrastructure automatically provisioned on creation. No more manual setup steps before your first deploy. Create an org, add a service, and you're ready to build.

Connect your GitHub repositories directly to Suga for source-linked builds.

How it works#

1. Connect: Click "Connect GitHub" in your project settings. A popup-based OAuth flow installs the Suga GitHub App on your account or organization.
2. Link a repo: In the build configuration for any service, select which GitHub repository to link.
3. Build: When you trigger a deployment, Suga pulls the source from your linked repo and builds the container image.
4. Trace: Each build shows the commit hash, author, and a direct link back to the source on GitHub, making it easy to trace what's deployed to the code that produced it.

Features#

• Popup-based OAuth flow (no redirect away from the dashboard)
• Per-build author attribution and commit links
• GitHub App permissions management from the settings page
• Works with both personal accounts and organizations

The dashboard now shows org-level resource limits and enforces CPU-to-memory ratios per tier. A banner in the changes panel warns you when you're approaching limits before you deploy.

• Minimum memory ratio enforcement to prevent misconfigured pods
• Validation messages match the enforced limits exactly
• Clear upgrade path when you hit the ceiling on your current tier