Early access — founding-user spots are limited

You build the product.
It runs the infrastructure.

Project Z watches your servers, diagnoses incidents, and applies governed fixes — autonomous monitoring, diagnosis, and recovery for founders who don't have a DevOps team.

Join the waitlist

Built for founders who are also the ops team

Every hour spent on infrastructure is an hour not spent on product, users, or revenue.

🌙 Incidents pick the worst time

Downtime doesn't wait for office hours. You're debugging from your phone at 3am, or finding out from a customer email at 9.

🚀 Every deploy is a gamble

No staging team, no release manager. One bad migration and you're restoring backups instead of shipping features.

🧩 Tools that watch, but don't act

Uptime pingers and dashboards tell you something broke. None of them tell you why — and none of them fix it.

How it works

A closed loop that runs on your infrastructure, under your rules.

01 Observe

Connects to your servers and services. Watches health, logs, and metrics in real time.

02 Diagnose

When something degrades, it reasons about the cause — not just the symptom that paged you.

03 Recover

Applies the fix only if your policy allows it. Restarts, rollbacks, scaling — all governed.

04 Learn

Every outcome feeds back in. Repeat incidents get resolved faster, or prevented entirely.

Autonomy you can actually trust

"An AI touching production" should scare you. That's why governance comes first.

📜 Policy-gated

Nothing executes outside the rules you set. You define what it may touch, and when.

👓 Dry-run by default

Start in observe-and-propose mode. Promote actions to autonomous only when you're ready.

🛑 Kill switch

One click halts all autonomous activity, instantly, everywhere.

🧾 Replayable audit log

Every decision is recorded, hashed, and replayable. You can always answer "why did it do that?"

Get early access

Founding users get hands-on onboarding directly with the builder and founding pricing, locked for life.

No spam. One email when your spot opens. Unsubscribe anytime.

FAQ

Will it touch my production without asking?

Not unless you tell it to. Project Z starts in dry-run mode: it observes, diagnoses, and proposes. You promote individual action types to autonomous execution when you trust them — and a kill switch stops everything instantly.

What does my stack need to look like?

The early-access focus is Docker-based stacks on a VPS or cloud VM — the typical solo-founder setup (app containers, a database, Redis, nginx). If that's roughly you, you're in the target group.

What does it cost?

Founding users get a flat founding price, locked for life, and direct access to the builder. Exact pricing is shared when your spot opens — it's deliberately cheaper than one hour of incident response per month.

When do I get access?

Onboarding is hands-on and in small batches, in waitlist order. First batch within weeks, not months.

Who's building this?

Ziad Merjane — software engineer building Project Z in public. Early users talk directly to me, and what you report shapes what gets built.