Product updates

Changelog

What’s new, what’s improved, and what’s fixed.

Product updates from Simplifyd Cloud, newest first.

20 November 2026 — Domains, faster delivery, and easier deployments

This November update covers changes through 20 November: more control over domains and DNS, delivery settings for static sites and public buckets, Supabase setup, and improvements to deployments, the console, and automation.

Custom domains for public buckets

Serve files from a public bucket on your own hostname, such as cdn.example.com. Add the hostname in the bucket’s Settings and follow the ownership and DNS instructions. The custom domain serves reads; S3 uploads and management continue through the S3 endpoint. Remove custom domains before making the bucket private.

Domain ownership checks

New custom domains now require proof of ownership before traffic is routed or an HTTPS certificate is issued. This applies to services, gateways, static sites, buckets, and video playback domains, including wildcards.

The console shows the TXT record to add and a Check now action. Domains hosted in your workspace’s delegated DNS zone can be verified through that zone. Verification activates routing without applying unrelated pending service changes.

HTTP/2 and compression

Static sites and standard public buckets now have independent HTTP/2 and Compression controls under Settings → Performance. Both are off by default. HTTP/2 lets browsers reuse one HTTPS connection for multiple requests, with HTTP/1.1 fallback. Compression uses gzip for supported text responses when the browser accepts it.

The settings apply to the platform URL and custom domains. Save and apply the change in the console; routing can take a few minutes to update. API clients can save either setting and then deploy to apply it. A follow-up fix keeps HTTP/1.1 storage backends working when the browser-facing site uses HTTP/2.

Static sites guide · Buckets guide

DNS traffic policies and delegation visibility

Create DNS traffic policies alongside a zone’s records. Define address pools, set weights, order failover pools, and add optional HTTP or HTTPS health checks. Ordered rules can select a pool by network, country, ASN, or continent, followed by a default pool for everyone else. The first matching rule wins.

Location and network matching use the visitor’s DNS resolver, which may be somewhere else. The editor makes rule order, address shares, and validation errors visible before you save.

Domain pages now show the nameservers returned by the registry, flag missing or mixed nameservers, and warn when a live domain has moved away. Check nameservers works on live domains too. Pending zones show their removal date, and zone overviews include a breakdown of record types.

Nigerian domains and more reliable search

Register .ng and .com.ng domains with naira pricing. Multi-year registration quotes now follow the registrar’s charges. Domain search keeps successful results when another lookup fails, and renewal-price lookups run together to reduce waiting. Registration rejection and registrant-verification events are also handled more clearly.

Laravel deployments from GitHub

Managed GitHub builds add a Laravel setup flow where enabled. Choose a repository, branch, and app directory; the platform detects Laravel and builds PHP, Composer dependencies, and optional frontend assets. Optional services include a worker, scheduler, Redis, object storage, and email.

Pushes to the selected branch can queue builds through verified GitHub webhooks. The console shows build status, logs, and retries. Database migrations run before the web release switches; a failed migration leaves the previous release serving. Managed builds are opt-in and require the GitHub build integration to be enabled.

Supabase on Simplifyd Cloud

The Supabase guide now covers creating the template from the dashboard or CLI, starting Postgres before the other services, opening Studio, copying app connection values, supplying initial SQL, and configuring Auth email.

The template includes Postgres, Auth, REST, Realtime, Storage, and Studio. Edge Functions, Storage image transformations, the Supavisor pooler, and Studio log views are unavailable in this template. Use Simplifyd’s deployment logs to inspect services.

Supabase setup guide

A clearer console and easier agent setup

Connect AI Agent is now available from the project canvas and account menu, with the server URL and setup instructions for supported clients. Connected Applications links land directly on the section where you can review and disconnect agents.

The dashboard header, navigation, service panels, and canvas controls have been simplified. Fitting the canvas no longer enlarges a small number of cards beyond their normal size. Usage breakdowns keep service names and costs aligned on narrow screens, scroll horizontally when needed, and start with project groups collapsed.

API and documentation

  • Workspace tokens can manage DNS records and read the workspace balance with GET /v1/workspaces/{workspace}/balance.

  • The HTTP API reference has broader endpoint coverage, request and response examples, and instructions for listing and removing custom domains.

  • New dashboard guides explain managed Kubernetes and virtual machines, including access, deployment, and lifecycle actions. Both services remain in beta.

  • Connected-agent API access has more explicit scoping and workspace isolation checks.

Billing and reliability changes

  • New accounts no longer receive automatic sign-up credit. Fund the workspace wallet before deploying services.

  • The website’s published compute and volume rates have been aligned with billing.

  • Services are restarted when a suspended workspace is restored.

  • Stopped HTTP ZeroData proxies remove their public routes, and HTTP-mode proxies pass port 80 through.

  • TCP and UDP ZeroData proxy traffic is now metered for billing.

  • Video libraries refuse automated traffic by default; administrators can allow it for an individual library.

  • Computer pointer moves no longer hang when the pointer is already at the requested position, and VM disk provisioning has a fix for failed disk clones.

Open the console · Read the documentation