Release notes
Everything that shipped, in the order it shipped.
Product, platform and company changes, dated and written for a reader who wants to know what actually changed.
Releases
The release story so far.
Each entry lists what changed and what it means for someone running a project here.
Sylphx Cloud is the hosting product
The product boundary is now explicit: Cloud runs projects, previews, production and domains from git to production. This site carries docs, quickstart, pricing and status. Auth, data and AI stay separate products you connect with your own keys.
Zero-config health observability
Services deployed on Sylphx can expose a continuous health score instead of a binary up/down probe. The score combines event-loop lag, queue depth, error rate, memory pressure and dependency pings, and it drives drain/restart decisions at the runtime boundary with no app-side wiring.
Deploy service — general availability
Git-driven deploys, preview environments and rollbacks became available to everyone: connect a repository, push, and Sylphx builds and serves both environments.
Backup service — scheduled database backups
Backups run on a schedule rather than by hand: daily logical backups plus continuous write-ahead log streaming, encrypted at rest, with a published retention window of 30 days.
KV, Realtime & Search — three new services
Three hosted services joined the catalog: a key-value store with TTL support, a WebSocket pub/sub service with channels and presence, and full-text plus semantic search over your own data. All three are reachable through the generated SDK.
Early access
Early access opened: a free tier for every service, a typed TypeScript SDK covering the public contract, and one console to operate what you deploy.
Private beta
The first cohort of developers ran real projects on the platform. Their feedback changed API design, SDK ergonomics and the shape of the pricing model before general access.
Corrections
When we get something wrong, it is published.
September 2026
Entry wording tightened, figures withdrawn
The redesign revision of this page reworded several entries in place. Every rewrite is listed here rather than left silent. Withdrawn as unsupportable: build-speed multipliers ("3x faster deploys"), beta cohort size, and a "unified dashboard" line that contradicts the product boundary. Withdrawn as no longer true or never shipped: the `sylphx migrate health-checks` codemod (superseded design document only), "GitHub & GitLab" narrowed to the repository integration that exists, and the Search service removed from the February 10 entry although the service is still in the catalogue — that deletion was wrong and is reverted below. Tightened without changing meaning: the health-observability specifics (/healthz, the framework middleware list, the seven signals, the drain/restart thresholds, the SHA-256 audit chain and `sylphx health verify`), and the backup entry is restated around the retention and restore facts the security page publishes. The dated entries above remain the record of what shipped.
Why this section exists
A changelog with no corrections in it is usually a changelog that has been quietly edited. Publishing the correction — including when a claim was removed because it could not be supported — is how a reader can tell the difference between a maintained record and marketing copy that happens to be sorted by date.
The same applies to the policy documents: security, terms, privacy and cookies each carry their own revision date, and material changes are announced here.
About this page
What this page is, and what it is not.
- Entries
- 7 published releases, newest first, each with a date you can cite.
- Scope
- Customer-visible changes: deploys, previews, domains, observability, backups, pricing and policy.
- Editing policy
- Dated entries are the record. Where wording had to change, the change is named in Corrections above with its date rather than left silent.
- Roadmap
- Not published here. This page is history; planned work is not announced as if it had shipped. See the docs for current behaviour.
Pricing and policy changes are announced here too — this page is the announcement channel, not a marketing feed. There is no release newsletter; the feed is the same record as RSS, for a reader who would rather subscribe than visit. What the platform does today is in the docs, and what it costs is on the pricing page — the operative document if the two ever disagree.
Looking for the raw version? The platform publishes version and commit identity on the status page for the deployment currently serving traffic.