Platform & Infrastructure
Ship Faster. Break Less.
What are you building? Landing page, online store, portfolio…
Need a starting point? Try one of these:
Landing Page
Online Store
SaaS Dashboard
Portfolio
Docs Site
SOC 2 Type II
99.99% uptime
Trusted by 4,000 teams
Support in under an hour
How It Works
From Commit to Live in Three Steps
No release window, no runbook, and no meeting to decide whether today is a good day to deploy.
Median deploy over the last 30 days, from commit to healthcheck.
01
Connect Your Repository
Point us at a repository and the framework, build command and runtime are detected for you. Nothing to install locally, and no YAML to write before the first deploy.
02
Open a Pull Request
Every branch gets a real, isolated environment in seconds. Reviewers open a link and see the change running, rather than a screenshot of it in a comment thread.
03
Merge and Ship
Merging releases to production behind a health check, with logs, traces and metrics on one timeline from the very first request.
Before You Switch
You’ve Felt This Before.
Every team gets here eventually — a CI runner, a hosting panel, a secrets vault and a monitoring dashboard that were never meant to share a login.
The Old Stack
Weeks to Provision: CI, staging infrastructure and monitoring set up separately before the first deploy ever runs.
A Tool Per Job: Six different dashboards for build, secrets, logs, alerts, previews and access control.
Long-Lived Shared Keys: One .env file, copied between machines, rotated only when someone remembers to.
Debugging by Guesswork: Logs in one tool, traces in another — no way to follow one request across both.
One Platform
Live in Minutes: Connect a repository and the first preview environment is running before the meeting ends.
One Dashboard: Build, secrets, logs, alerts, previews and access control in a single pane.
Tokens That Expire: Every credential is scoped to one environment and expires automatically, with an audit trail.
One Request, One Trace: Logs, traces and metrics live on the same timeline, so root cause is one click away.
Platform Architecture
Why We Built It This Way.
A closer look at how the platform holds up against the alternatives teams actually migrate away from.
Architecture
system.engine
Git-Native, Zero Server
Push a branch, get a URL. Build, release and health check run on our edge — nothing to patch.
A VM You Maintain
Runners, agents and OS patches are your job, on a schedule that competes with everything else.
Proprietary Build Queue
Deploys run on the vendor’s own worker fleet, on their release cadence, not yours.
Closed Visual Engine
No build step to inspect. Output is whatever the drag-and-drop layer decided to emit.
Secrets & Access
audit.trail
Scoped, Short-Lived Tokens
Every credential is scoped to one environment and expires — an audit trail answers “who changed this?” in one click.
Long-Lived Shared Keys
One .env file, copied between machines, rotated only when someone remembers to.
Vendor-Held Secrets
Stored in the platform’s own vault, with export tooling that lags the import tooling by design.
No Secrets Concept
Credentials, if any, live in the same account as the site — no separation between build and runtime.
Observability
insight.depth
One Timeline, No Blind Spots
Logs, traces and metrics from the same timeline — a slow request is one click from the line that caused it.
Bolted-On Monitoring
A separate APM agent to install, configure and pay for, disconnected from your deploy logs.
Basic Request Logs
Enough to see something broke, rarely enough to see why — deeper tracing is an upsell.
No Observability
Uptime is the platform’s problem to solve, invisibly — you get a status page, not a trace.
Who It’s For
Built for Every Stage.
From a weekend project to a compliance review — the same platform, sized to fit.
Solo Builders
Ship a side project without provisioning infrastructure you’ll only use once — one dashboard, one bill, live in minutes.
Product Teams
Every pull request gets a real preview environment, so reviews happen on the actual thing — not a screenshot in a comment thread.
Regulated & Enterprise
SSO, SCIM and an audit trail your security review can actually read — without a quarter of custom tooling to get there.
Platform
One Platform, Six Fewer Tools.
Everything below ships on every plan — no add-ons, no per-seat surprises.
Instant Environments
Every branch gets a real, isolated environment in seconds — reviewers see the change running, not a screenshot of it.
Edge Delivery
Assets and responses served from the node nearest your visitor, with cache rules you can reason about.
Secrets & Access
Scoped credentials, short-lived tokens and an audit trail that answers “who changed this?” without a war room.
Observability
Logs, traces and metrics from the same timeline, so a slow request is one click from the line that caused it.
Integrations
A documented API, webhooks that retry properly, and first-party connectors for the tools your team already runs.
Accessibility Checks
Contrast, focus order and landmark checks run on every preview, so problems get caught before a release does.
Capabilities
Built to Run What You’re Already Building
No rewrite required — bring the stack you already have, and it just deploys.
Any Framework
Next.js, Astro, Remix, or a plain static build — detected automatically, with nothing to configure by hand.
Any Database
Bring a managed database or your own connection string — pooling and TLS are handled for you either way.
Any Workflow
GitHub, GitLab, or a bare git remote — the same preview-per-branch flow either way.
Pricing
Priced Per Project, Not Per Seat.
Every plan includes the full platform. Move up when you need more capacity, not more features.
Starter
For solo builders and side projects
€19/ month
- 3 projects
- Preview environments
- 7-day log retention
- Community support
Team Most popular
For teams shipping every week
€79/ month
- Unlimited projects
- Full observability suite
- 90-day log retention
- 1-hour support response
Scale
For organisations with compliance needs
Custom/ annual
- Everything in Team
- SSO and SCIM
- Dedicated capacity
- Named support engineer
Customers
In Their Words.
Three teams who moved off a stack of stitched-together tools.
We cut our release process from a half-day ritual to something a junior engineer does on their second week. Nothing about that was luck.
Engineering leadLogistics platform, Rotterdam
The audit trail alone paid for the migration. Our security review went from three weeks of screenshots to an afternoon.
CTOFintech startup, Berlin
Preview environments changed how our designers work. They stopped filing tickets about screenshots and started reviewing the real thing.
Head of productSaaS company, Amsterdam
The Short Version
See It At a Glance.
Same platform, fewer words — for when you just want the answer.
Edge Delivery
cache.rules
Global by Default
Every response cached at the edge automatically.
DIY CDN
You wire up and pay for your own CDN.
Single Region
One data centre, unless you pay to add more.
Vendor CDN Only
Fixed to whatever the platform bundles.
Integrations
webhooks.native
First-Party Connectors
Webhooks that retry, no glue code required.
Script It Yourself
Every integration is a custom job.
Marketplace Add-Ons
Paid plugins, each with its own bugs.
Locked to Native Apps
Only what’s in the builder’s own app store.
Accessibility
a11y.checks
Checked Every Preview
Contrast and focus order caught before release.
Manual Only
Runs if someone remembers to run it.
Not Included
A separate audit tool, billed separately.
Template-Dependent
Only as accessible as the template you picked.
Time to First Deploy
time.to.live
Minutes
Connect a repo, get a URL.
Hours
Provisioning runners and pipelines first.
A Day or More
Waiting on a build queue you don’t control.
Minutes
Fast, but locked to the builder forever.
Pricing Model
billing.shape
One Predictable Bill
Every feature is included at every tier.
Sum of Many Bills
CI, hosting and monitoring — each with its own invoice.
Usage Surprises
A busy month can double the bill overnight.
Per-Seat Creep
Price climbs with every teammate you add.
FAQ
Frequently Asked Questions
Straight answers to the questions we hear most before a team signs up.
How long does migration take?
Most teams have their first project running the same afternoon. A full migration — every service, every environment — typically lands inside two weeks, and we do not charge for the overlap period while you run both.
Larger organisations with compliance requirements usually plan for a quarter. We will map that out with you before you commit to anything.
What happens when we outgrow a plan?
Nothing breaks. You will see a notice in the dashboard well before you hit a limit, and we will never throttle a production deploy because of billing.
Upgrades take effect immediately and are prorated. Downgrades take effect at the end of the billing period.
Can we self-host?
Yes, on the Scale plan. You get the same control plane running inside your own cloud account, with updates you apply on your own schedule.
What does support actually cover?
Real engineers, not a ticket queue that reformats your question back at you. Team plans get a one-hour first response during business hours; Scale plans get a named engineer and an on-call escalation path.
Every Plan Includes
Migration Playbook
A step-by-step plan tailored to your stack.
Onboarding Call
A guided walkthrough with an engineer, not a bot.
Usage Reports
A weekly digest of deploys, uptime and cost.
Team Training
Get your whole team comfortable with the platform.
Priority Support
Skip the queue with a one-hour response time.
Security Review
A joint pass over access, secrets and audit logs.