What we shipped.

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.

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.

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.

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.

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 for each part of the system.

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'".

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

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.

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.