Changelog

What’s changing in SaveOn.

A public record of product improvements across provisioning, local billing, developer workflows, monitoring, and account security.

August 2026 — Developer workflow foundation

SaveOn now provides a provider-neutral terminal workflow for listing databases, checking status, retrieving connection details when needed, and creating new workspaces through the v1 API.

The public developer documentation explains API-key setup, safe credential storage, and the command structure without exposing internal infrastructure names.

Terminal CLI foundation
API-key authenticated database commands
Public CLI documentation
Provider-neutral operational language

August 2026 — Billing and provisioning clarity

Customer-facing package prices continue to come from the live pricing service. Final amounts are displayed in Naira after server-side resource-rate transformation, markup, and platform operations reserve.

The database workspace continues to expose region labels, service state, reservation state, and monitoring signals where available.

Live Naira pricing
Wallet-based provisioning
Supported region selection
Operational workspace visibility

August 2026 — Account security

Password recovery now uses one-time expiring links and generic request responses. This helps users recover access while reducing unnecessary account-enumeration signals.

Email verification, API-key protection, and deliberate connection-detail access remain part of the account security workflow.

One-hour reset links
Single-use reset tokens
SMTP delivery through the existing email configuration
No password or connection secret in reset messages

How we document releases

Changelog entries describe user-facing behavior and operational outcomes. Internal provider names, secrets, infrastructure identifiers, and customer data are not included in public release notes.

For breaking API changes, the developer reference should be checked alongside the release entry before updating an integration.

Frequently asked questions

Where can I report a regression?

Use the support contact route and include the page, action, timestamp, and exact error message. Do not include passwords, API keys, payment secrets, or full connection strings.

Does a changelog entry guarantee availability for every account?

Some changes may roll out progressively or depend on account configuration. The product UI and API response remain the source of truth for your workspace.

Continue exploring SaveOn

Choose the next resource for your project, from practical documentation to pricing, security, and support.