Suga Changelog

A better view of your projects

Thu, 16 Jul 2026 00:00:00 GMT

The projects page used to be a plain grid of names. Now each card gives you a quick sense of what's actually inside a project before you open it. Every card surfaces: - The most recently active environment and its status at a glance. - A preview of that environment's resources: services, functions, databases, and volumes. - Compact CPU and memory meters showing what's allocated against your limits. - A footer with environment and resource counts and when the project was last updated. - Recent deployment activity. We've also added search and sorting, so finding the right project is quick once you've got a few of them. Sort by name, last activity, or when it was created. ![The redesigned projects index](/screenshots/changelog/054-projects-index-redesign/projects-index.png)

A clearer deployment history

Wed, 15 Jul 2026 00:00:00 GMT

The history panel has been rebuilt around the thing you actually scan for: what changed, and when. At first glance you can see the status, who started the deployment, when the deployment happened, the commit message, and how many resources were created or destroyed. Expand to see the details. ![The redesigned deployment history panel](/screenshots/changelog/053-deployment-history-redesign/history-panel.png) Selecting a past deployment no longer snaps your canvas to it. You preview it and apply the historical state deliberately, with a separate button, so browsing history can't clobber unsaved work. You will also be able to see active deployments in this list. We've also updated the flow of the apply, with commit messages now being required. To keep that from being a chore, you can generate a short summary of your changes as the default message. Now every entry in the history carries something meaningful even when you don't type one yourself. ![The redesigned review changes](/screenshots/changelog/053-deployment-history-redesign/review-page.png)

Smarter Docker Compose imports

Tue, 23 Jun 2026 00:00:00 GMT

Importing a compose file with a lot of shared configuration used to mean a lot of repeated typing. A stack like Supabase reuses the same values, such as a database password or a signing secret, across many services, and we were asking you to fill each one in every service that used it. Two changes fix that: - **Shared variables are asked for once.** When the same variable shows up across multiple services, we now set it up as an environment-level secret that each service references, instead of a separate copy per service. The import form groups these as shared, so you fill in a database password once rather than ten times. - **Variables inside connection strings are picked up.** Values embedded in a larger string, like a password inside a `postgres://` URL, used to be missed entirely. They're now detected and surfaced alongside everything else. The result is a much shorter form when you import a real-world stack, and fewer chances to fat-finger the same secret into a dozen boxes. ![Configuring environment variables while importing a Docker Compose stack](/screenshots/changelog/055-smarter-compose-imports/compose-import.png)

TCP proxies are now a paid feature

Thu, 18 Jun 2026 00:00:00 GMT

Public TCP proxies are moving to paid plans. On the free tier you'll still see the option in the public networking config, but it now sits behind an upgrade prompt. For existing applications with TCP proxies, there is no migration to do. These will continue to work and won't be torn down. The change will only apply to creating new TCP proxies. Those on Pro and Enterprise plans are unaffected. Public TCP proxies are a power-user capability: most legitimate free projects never reach for them, yet we were seeing them frequently for users who were running antagonistic workflows. Gating them to paid plans keeps the free tier focused on trying Suga out and lets us keep it generous for everyone using it as intended. If you have a legitimate reason for trying out TCP proxies you can reach out to us at support@suga.app and we can arrange a trial.

Deploy on Suga buttons

Wed, 10 Jun 2026 00:00:00 GMT

You can now turn any Git repo into a one-click deploy. Drop a "Deploy on Suga" button in your README, and anyone who clicks it lands in Suga with your project ready to configure and deploy. If your repo already has a compose file, that's all you need. Suga reads it, wires up the services, and asks for any variables before deploying. No extra config to maintain alongside your project. It works from a signed-out state, so the button is genuinely one click for whoever finds your repo. It's an easy way to share a working template, hand someone a starting point, or let people try your project without walking them through a setup. Adding one is two lines of markdown. Point the link at your repo and use our badge as the image: ```md [![Deploy with Suga](https://suga.app/badge.svg)](https://dashboard.suga.app/new/template?repo=your-org/your-repo) ``` Swap `your-org/your-repo` for your GitHub repo and you're done. A few options if you need them: - If your compose file isn't on the default branch or at the repo root, add `&branch=` and `&path=` to the link. - To point straight at a compose file anywhere, use `?compose=` instead of `?repo=`. - For READMEs with a dark background, swap the badge for `https://suga.app/badge-light.svg`. This will render like this: {/_ TODO: add screenshot of the import landing flow _/}

Persistent logging and a new log explorer

Tue, 09 Jun 2026 00:00:00 GMT

Until now, logs were real-time only. You could read them whilst the service was running but as soon as it was replaced during a deployment or restart, the previous logs were no longer accessible. Logs are now retained, and there are two new places to work with them: a dedicated Logs explorer for each environment, and a refreshed logs tab in the service panel on the canvas. The new explorer is available from the sidebar. It has a bunch of new features: - Search by keyword across all your services, and filter by service and level (info, warn, error, debug). - A volume histogram above the stream, stacked by level, so a jump in errors is easy to spot. - Time ranges from 5 minutes to 14 days, preset or custom, with longer history on paid plans. - Click any line for a detail panel: the full message, parsed fields, stack trace, and a permalink you can send so a teammate lands on the same entry. - Live mode to watch entries stream in, or page back through a fixed window. - Copy the lines on screen, or export the filtered set to CSV or JSON. The logs tab on a service got the same treatment. Filter by log level inline and open the full explorer with that service already selected when you need more than a quick look. The UTC/local toggle, replica toggle, and follow/tail are all still there for quick debugging. ![The logs tab in the service sidebar](/screenshots/changelog/050-logs-explorer/sidebar.png) If a spike shows up in your per-replica metrics, you can now jump straight to the logs to find out what caused it. ![The Logs explorer](/screenshots/changelog/050-logs-explorer/logs.png)

Duplicated services no longer share a build

Wed, 27 May 2026 00:00:00 GMT

If you duplicated a service that had a GitHub build wired up, the original and the duplicate ended up pointing at the same build configuration. Editing one would silently change the other. Each duplicate now gets its own.

Clearer errors for Cloudflare-proxied custom domains

Wed, 27 May 2026 00:00:00 GMT

If your custom domain's CNAME was proxied through Cloudflare (the orange cloud), Cloudflare answers DNS with its own edge IPs and hides the record Suga checks for. Verification would fail with a generic "CNAME not found" message, with no hint that the proxy was the cause. Suga now detects when a record is being proxied through Cloudflare and tells you exactly what to fix: set the CNAME to "DNS only" (the gray cloud), then verify. No more guessing why an otherwise correct record won't validate.

More control over builds

Wed, 27 May 2026 00:00:00 GMT

Some frameworks bake env vars into the output at build time rather than reading them at runtime. Vite is the obvious example: anything prefixed `VITE_` gets inlined into the bundle when `vite build` runs. Until now Suga only supported runtime env vars, so frameworks that needed values during the build couldn't see them. You can now set build-time env vars on any service, available for both auto-detect and Dockerfile builds. Custom build and start commands are also configurable for auto-detect, so you can override what Suga's framework detection picked if it didn't match what your project actually does. ![Build-time env vars](/screenshots/changelog/049-build-env-vars/build-vars.mp4)

Knowing when your Suga URL is live

Mon, 18 May 2026 00:00:00 GMT

It wasn't always clear when your Suga URL was actually live. Adding a generated URL made the row in the dashboard look ready right away, even though the service still had to be redeployed before traffic flowed. Hitting a `*.suga.run` host that wasn't currently routed would land you on a generic gateway error, with nothing to say whether the route was wrong, the deploy had been torn down, or the platform was broken. Both are sorted now. Custom domain rows show a clear pending state with a redeploy prompt right in the row, and unrouted `*.suga.run` hosts serve a branded Suga page that explains the hostname isn't routed yet. ![Suga fallback for an unrouted subdomain](/screenshots/changelog/045-deployment-polish/fallback-page.png)

Undo a typo, not the canvas

Mon, 18 May 2026 00:00:00 GMT

Hitting `ctrl+z` while typing in a sheet used to undo your last canvas edit instead of fixing your typo. Same story for redo and a handful of other shortcuts that fired when you didn't mean them to. Canvas shortcuts now stay out of the way while you're typing.

A new new project flow

Thu, 07 May 2026 00:00:00 GMT

We've updated the flow for new projects so there's more direction on what you can do. We used to just put you on an empty canvas, but now there's a proper `/new` page that asks where you want to start before it goes off and creates anything. There are three new options: - **Import a GitHub repo**, where you pick a repo and configure the build before deploying. - **Start from a template**, and once you pick one and fill in any env vars it needs, you end up with a project that's already wired up. - **Start with an empty project**, which is the same path it always was for getting to a blank canvas. This is all available from an unauthenticated state, so you can start adding "Deploy to Suga" buttons to all your project READMEs. ![New project flow](/screenshots/changelog/044-new-project-flow/new-project.mp4)

Empty repo imports

Wed, 22 Apr 2026 00:00:00 GMT

If you tried to import a repo you'd just pushed commits to, you might have seen it show up as "empty" and refuse to import, leaving you stuck with no obvious way forward. Fixed now. Worth sharing the lesson: the GitHub API exposes a `size` field on each repo, and `size === 0` is a tempting shortcut for detecting empty ones. It isn't reliable. That field is updated by a background job on GitHub's side that can lag by up to an hour, so a repo you just pushed to can still report zero size well after the fact. We now detect empties at the branch-fetch stage instead: no branches, no commits, nothing to import. Repos with actual content sail through, regardless of what `size` claims. ![Empty repository state](/screenshots/changelog/043-empty-repo-imports/empty.png)

Builds are up to 2x faster

Mon, 20 Apr 2026 00:00:00 GMT

Builds from a git repo now run end-to-end inside the builder itself. The clone and build-plan step used to run on a separate worker before handing off, which meant copying your repo across the wire twice. Now the builder fetches your code directly and goes straight into the build. For most repos this lands up to 2x faster, with no action needed on your end.

Build log fixes

Thu, 16 Apr 2026 00:00:00 GMT

If you noticed your build log freezing mid-build, that wasn't you. Fixed now, along with a couple of related quirks. - Logs will reliably stream live as the build runs. - Logs consistently show up on completed builds too, not just in-progress ones. - If your connection drops mid-build, it reconnects and picks up where it left off. ![Build Log Improvements](/screenshots/changelog/041-build-log-fixes/build-log-fixes.mp4)

Redesigned canvas nodes

Mon, 13 Apr 2026 00:00:00 GMT

Service and volume nodes on the canvas have a new design with more useful information visible up front. - An icon bar on each service node shows git/image source, mount path, and network status without opening config. - Status is now split into live state (running, failed, deploying, warning) and change state (new, modified, deleted). Both are visible at the same time, so a running service with pending changes shows both. - If volumes are detached from their parent service, they now reposition near the parent node. Resolving an issue that caused volume nodes to be moved off screen. ![Canvas Nodes](/screenshots/changelog/039-redesigned-canvas-nodes/nodes.png)

UX fixes and polish

Mon, 13 Apr 2026 00:00:00 GMT

Handful of UI improvements: - The "enable Suga domain" option was hard to find and didn't prefill the port. It's now a clickable card with a default port. - We've improved the consistency of styling (borders, radius, etc.) for UI elements, such as inputs, selects, and autocompletes. - Services no longer require a private port. Public ports are automatic, so leaving private ports empty is fine. - Container errors in deployment logs now link to explanations, instead of just expanding the log line. ![Error](/screenshots/changelog/040-ux-fixes-and-polish/error.png)

Connection status and graceful degradation

Thu, 09 Apr 2026 00:00:00 GMT

Sometimes the connection between your browser and Suga's hosted infrastructure can drop, whether it's your internet going down or an outage on Suga's end. Previously, these issues could be confused with errors in your deployed resources. Now they're clearly identified as connection problems. - If sync disconnects, the canvas locks and shows a connection banner instead of stale or loading indicators. - If workflow statuses can't be retrieved, they show "unknown" rather than errors that look like your service is broken. - If real-time updates drop, a banner lets you know updates have paused. This was done along with an updated [Suga status page](https://status.suga.app/) for each part of the system.

Fuzzy search for GitHub repositories and branches

Thu, 02 Apr 2026 00:00:00 GMT

Searching for GitHub repositories and branches in your build config now uses fuzzy matching. Partial names and minor typos will still surface the right results instead of showing an empty list. When there's genuinely no match, the empty state now includes your search term so it's clear what was filtered: "No repositories found for 'docs'".

Canvas node positioning and selection fixes

Thu, 02 Apr 2026 00:00:00 GMT

A round of fixes to how nodes behave on the deployment canvas: - Services no longer appear behind the config panel when added to the canvas. Centering now accounts for the side panel width. - Adding a new service opens the config tab automatically. Switching between existing services preserves whichever tab you were on. - Unmounting a volume no longer sends it off screen. Detached volumes now reposition next to their parent node. - Undo after deleting a node restores it to its original position on the canvas.

Custom domains

Mon, 30 Mar 2026 00:00:00 GMT

It has always been possible to get public domains for Suga services, but now you can use a custom domain for your Suga services. Map your custom domain to any service on Suga, whether it's a root domain (`example.com`) or a subdomain (`app.example.com`) Suga will handle: - **DNS Verification** Suga checks that it's registered and detects your DNS provider. - **SSL Certificates** SSL is automatically managed, ensuring a secure connection without any setup from you. - **Traffic Routing** Routes all traffic to your service automatically. ## How it works 1. **Add a domain**: Enter the domain you want to use. 2. **Pick a port**: Choose which port on your service the domain should route to. 3. **Configure DNS**: Copy and paste the DNS record information into your provider. Once your DNS records are in place, Suga verifies ownership automatically and provisions an SSL certificate. You can track verification and SSL status directly in the dashboard, no manual steps required after the initial DNS setup. ## Details - Available on Pro (up to 10 domains) and Enterprise plans. - Each domain maps to a single service and port within an environment. - Apex domains require a DNS provider that supports CNAME flattening (Cloudflare, Namecheap, etc.). See the full documentation: https://docs.suga.app/reference/custom-domains ![Custom Domains](/screenshots/changelog/035-custom-domains/custom.mp4)

Service templates and discovery

Wed, 25 Mar 2026 00:00:00 GMT

Browse and deploy from a curated library of service templates with the new discovery UI. Templates cover common service types: web servers, data stores, workers, and more. Each template comes with pre-configured settings, environment variables, port mappings, and sensible resource defaults. ## How it works When adding a new service to the canvas, you can now browse templates by category instead of starting from a blank configuration. Select a template, customize the settings if needed, and deploy. Variable references between services are wired up automatically based on the template definition. Templates are designed to get you from zero to deployed as fast as possible, especially for common patterns like "web server + database + cache" that most projects need. ![Service template discovery](/screenshots/changelog/032-service-templates/discovery.mp4)

Environment variable forking

Wed, 25 Mar 2026 00:00:00 GMT

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. ![Environment variable forking](/screenshots/changelog/034-environment-variable-forking/forking.mp4)

Variable masking improvement

Fri, 20 Mar 2026 00:00:00 GMT

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.

App sidebar navigation

Thu, 19 Mar 2026 00:00:00 GMT

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. ![App sidebar](/screenshots/changelog/033-app-sidebar/sidebar-video.mp4)

GitHub integration UX improvements

Wed, 18 Mar 2026 00:00:00 GMT

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 ![Git connection card](/screenshots/changelog/030-github-integration-ux/github.mp4)

Circular reference detection

Fri, 13 Mar 2026 00:00:00 GMT

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. ![Circular reference detection](/screenshots/changelog/029-circular-reference/canvas.png)

Automatic redeployment on git push

Thu, 05 Mar 2026 00:00:00 GMT

Services will now automatically rebuild and update when you `git push` to your repository. ## What is Keel [Keel](https://keel.sh) 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.

Auto-provisioned build infrastructure

Tue, 03 Mar 2026 00:00:00 GMT

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.

GitHub integration

Mon, 02 Mar 2026 00:00:00 GMT

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

Resource limits and CPU/memory ratios

Tue, 24 Feb 2026 00:00:00 GMT

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 ![Resource limits banner](/screenshots/changelog/024-resource-limits/banner.png)

Suga Free tier

Tue, 24 Feb 2026 00:00:00 GMT

The free tier has been renamed from Hobby to **Suga Free**. The upgrade-to-pro banner can now be dismissed, and it respects your dismissal across sessions.

Infrastructure cost metering and credits

Tue, 17 Feb 2026 00:00:00 GMT

Suga now tracks infrastructure costs per service and supports a credit-based billing model. See what each service costs in terms of compute and storage, and apply credits to offset usage. - Per-service cost breakdown on the billing page - Credit balance and usage tracking - Upgrade prompts when approaching tier limits - Links to billing directly from deployment dialogs ![Cost metering](/screenshots/changelog/023-cost-metering/billing.png)

Canvas viewport improvements

Mon, 09 Feb 2026 00:00:00 GMT

Fixed several canvas viewport issues: - New nodes now center correctly in the viewport regardless of sidebar state - Fixed offset calculation when the sidebar is open, so nodes don't appear shifted - Volume deletion no longer causes sync issues that could desync the canvas state

Volume creation dialog

Mon, 09 Feb 2026 00:00:00 GMT

You can now create and configure persistent volumes directly from the canvas via a dedicated dialog. The dialog validates mount paths and storage sizes before creation, and includes tooltips on delete actions to prevent accidental data loss. ![Volume creation dialog](/screenshots/changelog/022-volume-creation-dialog/dialog.png)

Autoscaling configuration

Thu, 05 Feb 2026 00:00:00 GMT

You can now configure service autoscaling directly from the canvas. Set CPU and memory thresholds, and Suga handles the HPA configuration on your cluster. - Per-service autoscaling rules - CPU and memory target thresholds - Replica limits enforced per tier - Real-time replica count visible on the canvas node When a threshold is exceeded, Suga scales the deployment up automatically. The canvas node updates in real-time to reflect the current replica count as pods come online. ![Autoscaling config](/screenshots/changelog/020-autoscaling/config.png)

Project navigation redesign

Tue, 03 Feb 2026 00:00:00 GMT

Project navigation has been redesigned with dedicated links for each project and a toggle-style switcher. It's now faster to jump between projects and environments without going through nested menus.

Suga Cloud

Thu, 29 Jan 2026 00:00:00 GMT

Introducing Suga Cloud: managed cloud operated by Suga. ## How it works Create a project, pick a region, and deploy. Suga Cloud provisions, sets up, and manages your infrastructure for you. Clusters are available in three regions: - **US** (North America) - **EU** (Europe) - **AU** (Australia) Upgrades, scaling, and networking are all handled automatically. You get the same canvas, metrics, logs, and autoscaling features as with a self-managed cloud, without the operational overhead. ## Pricing Suga Cloud is available on both the Free and Pro tiers. The Free tier gives you enough resources to experiment and prototype. Pro unlocks higher resource limits, more replicas, and priority support.

Color-coded replica logs

Tue, 27 Jan 2026 00:00:00 GMT

Log lines are now color-coded by replica. When tailing logs from a service with multiple replicas, each replica gets a distinct color so you can visually track which instance produced which log line. ![Color-coded logs](/screenshots/changelog/017-color-coded-logs/logs.png)

Volume management improvements

Mon, 26 Jan 2026 00:00:00 GMT

Volume management on the canvas has been improved: - Volumes can now be added and mounted directly from the compute node context menu - Improved cancel and unmount UX with clearer confirmation dialogs - Volume panel shows mount paths and storage class at a glance - Unique name generation for volumes to avoid conflicts ![Volume context menu](/screenshots/changelog/016-volume-management/context-menu.png)

Private container registry support

Tue, 20 Jan 2026 00:00:00 GMT

You can now pull container images from private Docker registries. Add your registry credentials in the service configuration and Suga handles the rest. Credentials are encrypted at the application level and never exposed in the UI after being set. - Supports Docker Hub, GitHub Container Registry, and most Docker-compatible registries - Credentials are write-only from the UI for security - Credentials are scoped per environment to prevent leaking between staging and production Credentials are encrypted at the application level before being stored. This means even database access doesn't expose plaintext registry passwords. ![Registry credentials](/screenshots/changelog/015-private-registries/credentials.png)

Resource name validation

Mon, 19 Jan 2026 00:00:00 GMT

Resource names are now validated before deployment to catch naming issues early. Previously, invalid names (too long, unsupported characters) would only fail at deployment with cryptic error messages. Now you get clear feedback in the UI before you deploy.

Async deployments

Tue, 13 Jan 2026 00:00:00 GMT

Deployments now run fully asynchronously with improved retry logic and exponential backoff. You can navigate away from the deployment view and come back later. The deployment continues in the background and its status is always up to date.

Real-time sync with Zero

Mon, 12 Jan 2026 00:00:00 GMT

The Suga dashboard now uses [Zero](https://zero.rocicorp.dev) as a real-time sync layer between the client and backend. ## Why Zero Traditional web apps fetch data from the server on every interaction and show loading spinners while waiting. Zero takes a different approach: it maintains a local cache on the client that stays in sync with the server via PostgreSQL replication. This means: - **Instant reads**: All data comes from the local cache, so the UI never blocks on network requests - **Optimistic mutations**: Changes appear immediately in the UI and sync to the server in the background - **Conflict resolution**: If two users edit the same resource, Zero handles the merge automatically ## What this enables The immediate benefit is a faster, more responsive dashboard. No more loading states when switching between projects or environments. Longer term, this architecture enables multiplayer editing. Multiple team members can work on the same project canvas simultaneously without overwriting each other's changes. Zero's conflict resolution ensures that concurrent edits converge to a consistent state.

Environment variable importing

Mon, 05 Jan 2026 00:00:00 GMT

You can now import `.env` files directly into your service configuration. Drop in an existing `.env` file and all key-value pairs are parsed and added to your service's environment variables. No more copying them one by one. ![Env file import](/screenshots/changelog/011-env-importing/import.png)

Google Translate compatibility

Tue, 30 Dec 2025 00:00:00 GMT

We fixed several issues where Google Translate broke the Suga dashboard for users with auto-translate enabled in their browser. ## The problem Google Translate works by walking the DOM and replacing `TextNode` elements with `` elements containing the translated text. This is fundamentally incompatible with React, which maintains references to the original DOM nodes. When React tries to update or remove a node that Google Translate already replaced, two things happen: 1. **Stale content**: React updates its reference to the old `TextNode`, but that node is no longer in the DOM. The translated `` element stays unchanged, so dynamic content like form values and status indicators stop updating. 2. **Crashes**: When React tries to call `removeChild` on a node that Google Translate already removed, it throws a `NotFoundError` that can crash the entire component tree. Martijn Hols wrote an [excellent deep dive](https://martijnhols.nl/blog/everything-about-google-translate-crashing-react) on this exact issue, which informed our approach. ## Our fix We took two approaches: 1. **`translate="no"` attributes** on interactive elements and dynamic content: dialog inputs, endpoint URLs, form fields, and status text that updates in real-time. This tells Google Translate to leave those nodes alone while still translating static UI labels and descriptions. 2. **Wrapping conditional `TextNode`s in `` elements**. When React conditionally renders a text node (e.g., `{isLoading ? "Loading..." : "Done"}`), Google Translate can replace the bare `TextNode` before React swaps it out, causing the `removeChild` crash. Wrapping these in a `` gives React a stable parent element to work with, which solved a large chunk of the crashes. This is not a perfect solution (as the blog post explains, there is no complete fix for this incompatibility), but it protects the critical paths where stale or broken content would cause real problems.

Auth UX improvements

Tue, 23 Dec 2025 00:00:00 GMT

The login and signup experience has been polished: - **Continue with GitHub/Google** buttons on the signup page for faster onboarding - Gradient loading states during authentication - Smoother transitions between auth states with no layout flash ![Login page](/screenshots/changelog/009-auth-ux/login.png)

Background workflows with Hatchet

Mon, 22 Dec 2025 00:00:00 GMT

Long-running operations like cluster initialization and deployment rollouts are now powered by [Hatchet](https://hatchet.run), an open-source durable execution engine. ## Why Hatchet We needed a workflow engine that could handle multi-step infrastructure operations reliably. Hatchet stood out for a few reasons: - **TypeScript-native**: Workflows are defined in the same language as the rest of our stack, no YAML or DSLs - **Durable execution**: If a step fails mid-workflow, it retries from where it left off rather than restarting from scratch - **DAG-based workflows**: Steps can run in parallel or sequence with explicit dependency graphs - **Step-level visibility**: You can see exactly which step a workflow is on and what failed ## What changed Cluster setup, deployment rollouts, and resource cleanup now run as Hatchet workflows. Each step has its own retry policy and timeout, so transient failures (like a cloud API being slow) are handled automatically without failing the entire operation. Progress is tracked per-step, so the UI always reflects exactly where things stand.

Deployment history

Tue, 16 Dec 2025 00:00:00 GMT

Every environment now keeps a history of past deployments. You can see what was deployed, when, and by whom. ## What's tracked Each deployment entry records: - **Who** triggered the deploy (user avatar and name) - **When** it happened - **What changed** in that deployment - **Status** (success, failed, in progress) The history view shows the 5 most recent deployments by default, with a "show more" button to load older entries. It refreshes automatically after each new deployment completes. ## Rollback If a deployment introduces a problem, you can roll back to a previous environment state directly from the history view. This restores the configuration as it was at that point in time and triggers a new deployment with the restored settings. ![Deployment history](/screenshots/changelog/007-deployment-history/history.png)

Service templates

Mon, 15 Dec 2025 00:00:00 GMT

We've added a library of pre-built service templates to speed up common deployment patterns. Instead of configuring a service from scratch, select a template and get a working deployment config with sensible defaults. ## Available templates - **Express** and **Fastify** for Node.js web servers - **Redis** for caching and message brokering - **WordPress** with pre-configured PHP and database settings - **PocketBase** for a lightweight backend-as-a-service - **MariaDB** for relational database workloads - **Uptime Kuma** for self-hosted uptime monitoring Each template includes pre-configured ports, environment variables, resource limits, and an icon. Templates that depend on other services (e.g., WordPress needing a database) automatically wire up variable references between them. ![Service templates](/screenshots/changelog/005-service-templates/templates.png)

Deployment stream reliability

Mon, 15 Dec 2025 00:00:00 GMT

Fixed an issue where long-running deployments could time out and lose their connection to the deployment stream. Deployments now maintain a stable connection throughout the entire rollout process, so you always see the final result.

Improved log streaming

Mon, 08 Dec 2025 00:00:00 GMT

Log streaming has been significantly improved for both build and runtime logs. - Fixed an issue where streaming logs could lock up the browser UI - Improved "follow" mode to reliably stick to the bottom of the log output - Resolved infinite build log accumulation that caused memory issues in long-running builds - Non-deployed containers now show a clear status message instead of an empty log view

Variable references in templates

Mon, 08 Dec 2025 00:00:00 GMT

Service templates can now reference environment variables from other services. When you add a template, any variable references are automatically wired up, making it easy to connect services that depend on each other (e.g., a web server referencing a database connection string). ![Variable references on the canvas](/screenshots/changelog/004-variable-references/references.png)

Per-replica metrics

Mon, 01 Dec 2025 00:00:00 GMT

Resource metrics can now be broken down by individual replica, or toggled to a merged view showing aggregate consumption across all replicas. - CPU and memory usage split per pod with individual charts - Merge toggle to combine metrics into a single weighted view - Replica names are displayed as badges for quick identification ![Per-pod metrics](/screenshots/changelog/002-per-pod-metrics/metrics.png)

Deployment canvas

Tue, 25 Nov 2025 00:00:00 GMT

Suga now includes a visual deployment canvas powered by [React Flow](https://reactflow.dev). Instead of editing YAML files and running `kubectl apply`, you manage your entire service topology on an interactive canvas. See containers, functions, environment variables, and their connections at a glance. Click into any node to configure it, drag to rearrange, and deploy changes with a single click. - Drag-and-drop node management for services and resources - Visual routing - Organization and project navigation with environment switching - Real-time deployment status indicators on each node - Figma-style panning and zoom controls ![Deployment canvas](/screenshots/changelog/001-deployment-canvas/deployment-canvas.png)