Sevalla Changelog #0080 Faster Paths to Production
MCP onboarding, usage alerts, zero-downtime credential rotation, and dashboard improvements for production teams.
Establishing connection…
Signal detected.
Link established.
Baud here with a 56k Sevalla changelog transmission.
Updates in this transmission:
Four platform updates shipped over the last two weeks. One reduces onboarding friction. One fixes dashboard navigation problems that slowed teams down. One gives teams better visibility into infrastructure spend. And one removes downtime risk during object storage credential rotation.
Less setup friction. Less operational guesswork. More time spent shipping.
Let's take a look.
Guided onboarding that gets you to production faster#
New users now land in a guided onboarding flow directly inside the Sevalla dashboard.
Not a marketing tour. Not a checklist pretending to be onboarding. An actual path to getting something running.
The new onboarding sheet gives teams four quick-start paths depending on what they want to do first:
- Connect a coding agent through MCP
- Deploy an application
- Deploy a database
- Launch a template
The featured path is MCP setup.
Why?
Because developers are increasingly using AI coding agents to build software faster, but most infrastructure platforms still force teams back into dashboards, YAML, and manual workflows the moment production enters the conversation.
That breaks velocity.
Sevalla's MCP integration lets coding agents interact directly with infrastructure through prompts. Generate an API key, connect your agent, and start deploying applications, databases, and infrastructure without stitching together additional tooling.
The onboarding flow now makes that setup immediate instead of buried in documentation.
Each path also works as a persistent checklist, so teams can move through setup incrementally without losing context.
Less wandering around the platform. Faster path to a real deployment.
The dashboard navigation no longer fights you#
We revamped dashboard navigation to remove one of the most common UX problems users reported:
Getting lost.
Previous navigation patterns separated core navigation and contextual navigation too aggressively. Moving between projects, services, and workflows required too much mental overhead.
That's now fixed.
Main navigation and contextual navigation are shown together, and the dashboard now uses a full-width layout.
This sounds small until you spend all day inside infrastructure tooling.
Production platforms should reduce cognitive load, not create more of it.
The result is faster movement across projects, fewer dead ends, and a dashboard that feels more operationally coherent during real production work.
Usage alerts for teams that actually care about spend control#
Usage-based pricing only works when teams can monitor usage before costs become a problem.
Now you can create usage alerts at both the company and project level.
Set:
- A spending limit in USD
- Multiple threshold percentages
- Multiple notification recipients
Thresholds trigger once per billing period and automatically reset for the next cycle.
This matters for growing production workloads where usage changes quickly across environments, staging systems, previews, AI workloads, or customer traffic spikes.
Instead of manually checking dashboards or waiting for invoices, teams now get proactive visibility into spend as infrastructure usage changes.
Operational visibility should include cost visibility too.
Rotate object storage credentials without taking clients offline#
Credential rotation is one of those operational tasks that sounds simple until production traffic depends on it.
Before this update, rotating object storage credentials often meant coordinating downtime windows, updating clients quickly, or accepting temporary disruption risk while applications switched to new keys.
Now you can rotate object storage credentials directly from the Sevalla dashboard or API without immediately invalidating existing clients.
When rolling credentials, you can:
- Expire old keys immediately
- Or keep old and new keys active together for up to 168 hours
That grace period matters for real production systems.
It gives teams time to update applications, CI/CD pipelines, edge services, background workers, and third-party tooling without breaking live traffic or interrupting uploads.
The same workflow is also available through the API:
POST /object-storage/{id}/rotate-credentials
Production infrastructure should not require risky maintenance windows for routine operational work.
Transmission complete#
Faster onboarding, cleaner navigation, proactive spend visibility, and safer credential rotation for production infrastructure teams.
More improvements on the way.
Awaiting next transmission.
Link closed.