Changelog

Database Studio now works with Redis and Valkey#

The Database Studio is no longer SQL only. Open Studio on any Redis or Valkey database and you get a full key-value workspace, with no redis-cli or third-party GUI needed.

Browse the keyspace: scan keys with pattern and type filters, switch between a flat key list and a namespace tree, and select multiple keys to delete them or set their TTL in one go. A database selector lets you move between logical databases.

Update every key type: dedicated editors for string, hash, list, set, sorted set, stream, and JSON keys, with JSON highlighting, bracket matching, and folding in the value editor. Add, rename, and delete keys, and manage TTLs with a live countdown.

Run commands: a redis-cli style console with autocomplete, command history, and an inline command reference.

Inspect the server: an overview of memory, clients, throughput, and keyspace, every INFO field in a searchable view, the slow log, and the list of connected clients.

You can also export the loaded key list to .csv or .json. See Database Studio for more.

Sevalla is moving to Oracle Cloud Infrastructure#

Starting in early September, Sevalla will begin gradually moving workloads from Google Cloud to Oracle Cloud Infrastructure.

The migration happens in waves, beginning with static site builds. For most customers, no action is needed.

Read the full announcement for migration details, expected impact, location changes, IP changes, and FAQs.

More control over how cron jobs run#

Cron jobs now expose two Kubernetes scheduling controls, so a run that hangs can no longer quietly wedge your schedule (the exact situation that used to leave a cron job stuck after a deployment until you recreated it).

Concurrency policy: decide what happens when a run is triggered while the previous one is still going:

• Forbid (default): skip the new run until the current one finishes. Nothing changes for your existing cron jobs.
• Replace: cancel the still-running job and start a fresh one. This is the self-healing option: a stuck run gets cleared on the next tick instead of blocking every run after it.

Max run time: optionally cap how long each scheduled run may take. If a run exceeds it, Kubernetes terminates it. Leave it empty (or set 0) for no limit.

Both settings live in your process settings and through the API (see Create process and Update process). They apply to cron processes only.

Railpack build strategy (beta)#

You can now build your applications with Railpack, the successor to Nixpacks. Railpack analyzes your repository and builds an optimized container image with zero configuration, powered by BuildKit.

To try it, choose Railpack as the build strategy in your application's build settings (Settings > Build strategy > Update build strategy). It is also available through the public API by setting build_type to railpack.

Railpack detects and builds Node.js, Python, Go, PHP, Java, Ruby, .NET, Deno, Rust, and Elixir out of the box. Custom start commands work the same way as with other build strategies: if your web process has a start command set, it overrides the one Railpack detects.

Railpack support is currently in beta. Nixpacks remains the default build strategy for new applications.

Purge your CDN cache in one click#

If you're serving stale content after a deployment or an upload, you can now clear it yourself, with no need to wait for the cache to expire or reach out to support.

We've added a new Cache section to the settings of both static sites and object storage. Head to Settings → Cache and hit Purge cache to instantly clear the cached assets served from our global CDN.

• Static sites: purges the CDN/Edge cache for your site. Reach for it right after a deployment when updated assets aren't showing up yet.
• Object storage: purges the CDN cache for your bucket, so freshly uploaded or replaced objects are served immediately.

The purge takes effect right away, and you'll get a confirmation the moment the cache is cleared. Available to anyone with update access to the service.