Zensu
Closed beta · waitlist open

From idea to release —
and back from your users.

The AI-native lifecycle manager that unifies your roadmap, sprint board, tests, docs, security reviews, and user feedback around the actual feature. Drive it from Claude Code, GitHub Actions, or your browser — with a release gate built in.

Request access Log in

No credit card. EU-hosted data, or self-host on Enterprise.

Works with Claude Code, Kiro, GitHub Actions, and the Zensu CLI today. More coming.

Claude Code Kiro GitHub Actions Zensu CLI Codex Soon
See it in 45 seconds

From roadmap to release — in motion.

The problem

Your features live in three disconnected worlds.

Code generation, project management, and DevOps each own a slice of the lifecycle. None of them treat the feature as a continuous, addressable entity.

Code generation

"How do I ship code faster?"

Claude CodeCursorCopilot

Project management

"What needs to be built?"

LinearJiraIssues

DevOps & observability

"Is everything running?"

GitHub ActionsArgoCDGrafana
Result: features get tracked in three places, lose context between them, and ship without anyone knowing if the docs, tests, or security review actually exist.
The loop

Every stage, on the same feature.

Code generation, project management, and DevOps each own a slice of the lifecycle. Zensu joins them into one continuous loop — the feature is the thread that runs through all of it.

  1. Idea A paragraph becomes a structured product.
  2. Plan Roadmap, sprints, and user journeys.
  3. Build One ID. CI flows in. Full audit trail.
  4. Gate Won't ship until it's ready.
  5. Release Versioned, tier-gated, documented.
  6. Monitor Live health — up, degraded, or down.
  7. Listen User feedback feeds the next idea.
user feedback feeds the next idea
The loop, live

Watch one feature travel the lifecycle.

The same loop — now in motion. The feature orbits each stage while the product builds itself on the right and Zensu shows the view that matters at that step. Hover a stage to preview it, click to pin. The core — governance, knowledge, docs — touches every stage.

Two ways in

Greenfield or brownfield. Same feature graph.

Start from a one-page idea, or point Zensu at an existing repo. Both paths end in the same place — a complete feature graph with components, security levels, and linked tests, docs, and source files.

Greenfield

Start from an idea

You have an idea, a PRD, or a one-pager. Zensu turns it into a structured product before you write a line of code.

  1. Capture the idea

    Drop in a vision, a PRD, or a one-pager — from your editor, the browser, or an import.

    vision docor import

  2. Zensu drafts the product

    It proposes components, prioritized features with effort estimates, a security level per feature, and the user journeys behind them.

    componentsfeaturessecurity levels

  3. Review, then apply

    Refine everything in a visual tree, then create the product, components, and features in one transaction with secure defaults.

    visual reviewsecure defaults

  4. Guided setup

    A focused wizard walks you through journeys, security, tiers, and a ready-to-commit CLAUDE.md.

    journeystiers
Brownfield

Bring an existing repo

You already have code, tests, and docs. Zensu reads them and reverse-engineers a feature inventory you can trust.

  1. Point at your repo

    Connect a GitHub, GitLab, or Bitbucket repository to the product.

    GitHubGitLabBitbucket

  2. Reverse-engineer features

    An agent reads the code and proposes confidence-scored feature candidates, each already linked to its real source, tests, and docs.

    confidence scoresauto-linked

  3. Review & approve

    Batch approve or reject, filter by component, and roll back an entire import in one click if something's off.

    batch reviewone-click rollback

  4. A live feature graph

    Apply, and every feature lands with its code, tests, docs, and a baseline version — ready for the gate.

    linkedversioned
Plan it. Run it. Ship it.

Your roadmap, your sprints, your packaging — on the same features.

No second tool to sync. The cards on your board, the bars on your roadmap, and the rows in your pricing matrix are the very features you build.

Built-in Scrum

Org teams, sprints, story points, and a burndown that updates itself from real releases.

Roadmap

Drag features across quarters on component swimlanes, with milestones and a today line.

Tier matrix

Hard, soft, or preview gating per feature — package your product in one inline-editable grid.

The release gate

It won't ship until it's ready — and it tells you why.

Set the bar once. Zensu refuses the move to released until a feature clears it — across security, tests, docs, and the user journeys it touches. Nothing reaches production half-baked by accident.

ZEN-42 OAuth login with PKCE in review
Release blocked — 409
  • Security review must be approved score 6.4 / 10
  • Threat model must be completed OWASP A07:2021
  • Test coverage above 80% 81%
  • Critical journeys healthy checkout · login
Security readiness
6.4/10
Auth9
Input validation8
Encryption7
Audit logging4
OWASP A07:2021GDPRSOC 2HIPAA

Tag any feature, set per-classification policy, and override with a logged justification when you must — the risk is on the record, not hand-waved.

Documentation

Docs for two audiences — that never quietly rot.

Link Markdown docs to a feature and aim each at your team or your users. Zensu scores how complete they are, flags the moment the code outran them, and publishes the public ones to a docs site on your own domain.

Second brain

Ask your whole product in plain English.

One question, one synthesized answer — drawn from every feature, doc, journey, wiki page, and design note you've indexed.

Close the loop

Hear your users. Watch it run.

Ship a feature and the loop comes back around: collect what users ask for on a public board, show them what's coming, and keep an eye on what's live — all without leaving Zensu.

live · up / degraded / down · 24h & 7d uptime api99.9%workerdegradedwiki100%
AI-native platform

The lifecycle manager — for the team around the developer.

Claude works in your editor. Zensu works across your whole team — the dashboards, audit trail, knowledge search, and compliance no CLI tool can deliver. German-operated, EU-hosted by default.

One view of everything

Portfolio dashboards across products — release-gate progress, security posture, journey health, the tier matrix — plus analytics on how much of your delivery is AI-driven.

Run it as a team

Invite PM, Security, and Compliance with per-role permissions, tag features GDPR / SOC2 / HIPAA, and export an audit log of every change.

A safe browser assistant

Read or change your whole product by chat. Every write surfaces as an approval card you click, and destructive actions are blocked outright — autonomy without the risk.

Yours to host, your way

EU-hosted in Germany on Open Telekom Cloud (BSI C5, ISO 27001) with your feature data at rest in the EU, or self-host on your own Kubernetes — air-gapped, zero outbound, no phone-home — for full data sovereignty.

Explore Enterprise
Who it's for

Built for teams that ship every week.

Zensu is opinionated about workflow, not about who's allowed to touch it.

Primary

Solo devs & indie hackers

Run 1–5 SaaS products in parallel, already on Claude Code and GitHub. Want overview without enterprise bureaucracy.

Secondary

Small dev teams (2–10)

Need feature ownership, per-feature coverage, and roadmaps that stay in sync with what's actually shipping.

Tertiary

PMs & non-technical founders

Have product ideas, can't read CI logs. Use the Product Studio to turn vision into a structured feature graph.

Quaternary

Designers & UX researchers

Link designs and research to specific features. See at a glance which features are still moving and which are frozen.

Dogfooding

Built with Zensu — including this page.

We run Zensu on Zensu. Every capability you just read about is a feature record inside Zensu itself — and so is the redesign you're looking at.

Yes — this page is a real ZEN-xxx record. The lifecycle you're reading about is the one that shipped it.

Strict TDD, every change

Shipped through a RED→GREEN cycle with a phase-gate that blocks any edit lacking a failing test first.

Five-perspective review

Every pull request runs parallel conventions, bugs, architecture, tests, and security reviews before it can merge.

Release-gated

Features don't reach released until tests, docs, and security checks pass — enforced by the lifecycle, not memory.

Ship features. Not status meetings.

Zensu is in closed beta. Request access and we'll email you the moment a slot opens.