What we are building next
An open view of where the platform is going. Dates are guidance, not promises — priorities follow whatever actually blocks your deploys.
In progress
Being built right now — partially available.- Q3 2026Preview environments per pull request
Ephemeral environments spun up for every pull request and torn down on merge, with their own URL and variables.
How deploys work → - Q3 2026Deeper MCP tooling for agents
More read and write tools exposed to assistants: logs, metrics and backup operations behind explicit confirmations.
Agents and MCP →
Next
Planned and scoped, work has not started yet.- Q4 2026Autoscaling by CPU and request rate
Today vCPU and RAM are set by hand. Automatic horizontal scaling with configurable limits comes next.
- Q4 2026Team accounts and roles
Shared projects with per-member roles, invitations and an audit trail of destructive actions.
- Q1 2027Public status page
Per-region uptime, incident history and subscriptions for platform events.
Exploring
Under research. No dates, no promises.- 2027App marketplace
One-click ready-made apps: CMS, bots, automation and monitoring. The catalog is being assembled — nothing is published yet.
Service types → - 2027Public API and CLI
Scripted service management from CI without opening the control panel.
Shipped
Live in the control panel today.- Jul 2026Backups and restore
Scheduled and manual backups for volumes and databases, restored from any stored copy.
Backups → - Jun 2026Rollback points on every build
Deploy history keeps successful builds so a service can return to the last working version in minutes.
Rollbacks → - May 2026Native Docker deploys
Dockerfile, compose file or an uploaded archive with automatic stack detection.
Creating services →
The full history of platform changes lives in the changelog.
Open the changelog →
