What we’re building next
No dates. A roadmap with dates on it is a list of promises someone is going to break — this is honest ordering instead. Things move up when people ask for them.
Last reviewed September 16, 2026. For what has already shipped, with dates, see the changelog.
Building now
1Actively in progress. These are the things most likely to land next.
Bitbucket repositories
The connection, webhooks and per-project secrets are written; it is not switched on yet. When it is, Bitbucket repos get the same push-to-preview flow GitHub and GitLab have today.
Next up
7Committed to, not yet started. Ordering can change if enough people ask for something further down.
Database branching
An isolated database per preview, seeded from a snapshot, so a migration on one branch cannot break another. Postgres first. This is the piece that makes a preview a genuine copy rather than a copy of the web tier.
Monorepo previews, properly
Pointing a preview at a subdirectory works today. What is missing is the rest of it: several services from one repo previewed together, workspace layouts detected without configuration, and a build cache that understands shared packages.
Deeper per-project analytics
The project Analytics tab already shows deploys, build times and success rate. Still missing: build-time p95 and the environment variables that most often break a build.
Environment variable groups
Define a set of variables once and attach it to many projects, plus per-branch overrides for the values that legitimately differ.
Interactive Slack actions
Build notifications already post to Slack. Next: redeploy, tear down, and open the preview from the message itself.
Run your test suite against the preview
Point Playwright or Cypress at a preview and have it run automatically on every deploy, with the result on the pull request.
Ticket linking
Attach the preview URL to the Linear or Jira issue it belongs to, and reflect the deploy status back onto the ticket.
Exploring
5Real problems we intend to solve, without a settled shape yet. Tell us if one of these is blocking you — that moves it.
Single sign-on
SAML and OIDC. Straightforward to build and firmly gated on somebody actually needing it — if that is you, say so and it moves up.
Durable audit log with export
Who deployed what, when, and from where — retained, exportable, and tamper-evident. Pairs with finer-grained roles than owner / admin / member.
Previews that never touch the public internet
Private networking for teams whose policy forbids an unreleased build being reachable by URL, however unguessable that URL is.
More than one region
Previews built and served closer to the team reviewing them, and an EU-only option for teams who need data to stay put.
White-label for agencies
Your branding, your dashboard domain, your client-facing product. Custom preview domains were the first step; the dashboard is not white-labelled yet.
Recently shipped
The dated version, including the fixes for things we had got wrong, is on the changelog.
- The MCP server is listed in the official MCP registry and starts without an API key
- GitLab previews, connected read-only by default
- Try a preview from the homepage without signing up
- Custom preview domains on Pro and above, with certificates issued for you
- Failed builds now report a cause, not just a red status — 36 diagnostic rules over the build log
- Build logs retained on the deployment, so the evidence survives the failure
- Preview a subdirectory of a repo through the API
- Setup guides for 14 frameworks
- A CLI, an MCP server, and a REST API
Need one of these sooner?
Email hello@previewdrop.dev and say which one and what it is blocking. That is the whole process, and it is the main thing that reorders this page.