Meerkat by Blank Cut
The platform that keeps watch over your apps.
Meerkat deploys, scans, reviews and alerts. Connect a GitHub repo, ship it to production with one command, and Meerkat keeps an eye on it from there, with Blank Cut's engineers behind it.
14-day free trial. No card to start.
- Repo to production
- 1 command
- Free to try
- 14 days
- Plans from
- $25/mo
- Run by
- Blank Cut
LiveDeploys. Scans. Reviews. Alerts.
A meerkat stands guard so the rest of the group can get on with things. Meerkat does the same for your apps: four jobs, done for every one of them, so you can get on with building.
Deploys
Connect a GitHub repo and merge the scaffolding pull request: a hardened Dockerfile, the build workflow and a deploy config. Then one command, or one button, ships it to your-app.blankcut.app or your own domain.
Scans
Your repo is checked for committed credentials and risky build steps. Every image the platform builds is scanned for known vulnerabilities before it is pushed, and re-scanned daily while it runs. The deploy gate stops a build with an unwaived critical or high finding.
Reviews
Every release is a change you can read. An AI deploy reviewer checks it against the image it pins and the app's live state before it merges, and anything it isn't sure of waits for a person.
Alerts
App health, restarts, logs and spend stream into the console. Alerts reach you in Meerkat and by email, and critical ones go to our platform team too.
The deploy gate is being switched on one app at a time. It already guards the apps we run ourselves, and you hear from us before it's on for yours; until then, findings are reported rather than enforced.
What it runs
Your whole app, not just the frontend.
The API, the database, the cache and the jobs that run on a timer, on one platform, with a team behind all of it.
Built into containers
Next.js and Vite frontends and Node, Python and Go services, each built into a container. No Dockerfile? We write a hardened one: multi-stage, slim and non-root.
Managed Postgres and Redis
Add a Postgres database or a Redis cache to an app, provisioned and wired in for you.
Scheduled jobs
Run one of your app's own endpoints on a schedule, as often as every five minutes. You write the endpoint; the platform calls it.
Gated secrets
Values live in an encrypted store and are injected at runtime. Your .env.example is the allowlist: a key it doesn't declare never reaches the app.
A CLAUDE.md for your agent
Every repo we scaffold ships with a CLAUDE.md that sets out the platform's conventions, so Claude Code builds inside them instead of inventing a new deployment every session.
Your code stays yours
It lives in your own GitHub repo, and everything we add arrives as a pull request you can read, review and revert.
Meerkat runs a deliberately small set of stacks so every app gets the same guarantees. See the supported stacks ↗
The Meerkat CLI
Everything in the console is in the CLI too, so you can work in a browser, a terminal or through your coding agent, on the same app. blankcut validate tells your agent what would fail before it opens a pull request.
With a team behind it
What else we build →The platform team is us
Cluster health, patching and alerting are ours. Your app and your repo stay yours.
Help with the app itself
When you want hands on your code, the engineers who build software for our clients can help, billed as support time.
Proven on our own work
The apps we host for clients, and our own products, run on the same platform.
Pricing
A base fee, then what you actually use.
Every plan starts with a 14-day free trial, with no card needed to start. Compute is metered hourly against an included quota; databases, domains and storage are billed per unit.
$25/ month
Your first app in production, on real infrastructure.
$50/ month
A few apps in production, plus room to prototype.
$100/ month
Production workloads, and billing your own clients.