Plan with live context
Compare desired topology with the environment the customer actually has.
1 request → 5 reviewable steps
Guided company launch
From one idea to a live product.
You describe the company. Your coding agent builds the product. PERCO gets the product, domain, email, and production system online.
Trusted by innovators
NVIDIAInception
AWSStartups
Googlefor Startups
Connected — your project is linked to the canvas, securely
What it is
Collects and manages subscription payments from PulseBoard customers, with receipts and plan upgrades handled for you.
Why you need it
Your idea includes billing — customers pick a paid plan when they sign up.
Monthly cost
~$12 / month at your expected starting volume. Scales only when revenue does.
Readiness
Configured and checked against the plan. Ready the moment you approve.
Nothing deploys without your explicit approval.
Full plan10 services~$86/mo est., all-in0lines of code shown
PulseBoardFeedbackRoadmapPricingSign in
Top feedback
96votesSlack notifications for new feedback
71votesExport responses to a spreadsheet
Public roadmap
Planned API accessTeams
In progress Dark mode
Shipped VotingBilling plans
Start with the idea. Nothing else.No diagrams, no setup, no technical decisions — the canvas holds only what the founder wants to exist.
02The path
An AI-native cloud. Real estate for your agents.
One governed path from a request to a live, inspectable system.
Deploy the whole stack
Build the app, install declared services, bind access, and publish the route.
10 services, one deploy
Verify before production
Record declared checks and require explicit approval before promotion.
7 checks · pass, fail, or skip
request → plan → deploy → verify → live
03Your agent has a seat
Give your coding agent a deployment surface.
PERCO CLI and MCP connect your agent to the control plane. Your agent writes code. PERCO ships systems.
Claude CodeCodexCursorCLI
> perco plan --project pulseboard Plan generated: pulseboard-plan-1042 > perco apply pulseboard-plan-1042 Deploying 10 services... ✓ Provisioning infrastructure ✓ Configuring services ✓ Running migrations ✓ Routing traffic ✓ Running verification ✓ Deployment live: https://pulseboard.app > perco open pulseboard Opening in browser...
04Read it before it runs
Reviewable changes
See the system
See the system
before it changes.
PERCO compares a desired EnvironmentGraph with live state and shows deterministic steps, risk, and blast radius. Apply is fenced against stale state.
RequestPlanChanges
Request
Web appDatabaseCacheDomainTests
Plan
Existing
NewUpdateNewNewNew
Summary
Change set
Steps5State fenceFreshRiskVisibleIdempotencyRequiredMCHuman operatorFinal apply authority
05Everything a product needs
A live product needs more than a web app.
PERCO connects the foundations your product declares, without hiding the boundaries or the proof.
Development & dataPrivate networking & securityProduction & public edge
06Receipts, not promises
Verification evidence
Proof ships with the deployment.
Each declared check records a result. Unsupported live probes remain explicit as skipped or inconclusive instead of being presented as passed.
Verification run
ScopeWebsite release
StateRecorded
Result modelPass / fail / skip
✓Evidence attached
| # | Check | Service | Result | Time | Map |
|---|---|---|---|---|---|
| 01 | Domain & TLS | Domain | Passed | 10:51:12 | |
| 02 | Database migrations | Postgres | Passed | 10:51:24 | |
| 03 | Role & permission grants | Auth | Passed | 10:51:36 | |
| 04 | Vector index query | pgvector | Passed | 10:51:45 | |
| 05 | Cache write / read | Redis | Passed | 10:52:03 | |
| 06 | Payment webhook | Payments | Passed | 10:52:18 | |
| 07 | Health check all services (live probe unsupported in preview) | All | Skipped | 10:52:40 |
07Day two, handled
Production is
Production is
a state, not a
launch moment.
Live systems are continuously observed, measured, and proven.
TimelineLogsMetricsDomainFirst request
Plan approvedHuman gateDeploy startImage buildHealth readyRuntime onlineServices upPrivate accessDomain liveTLS activeFirst request200 OK
Redacted log tail
10:58:42app started10:58:49health ready10:59:03TLS route10:59:21GET / 20010:59:26GET /roadmap 20010:59:38POST /api/feedback 20111:00:02digest queuedRecent metrics
CPU12%
MEM512Mi
P9584ms
Domain state
ClaimVerifiedTLSActiveDNSResolvedFirst request
GET /200 OKBrowserChromiumConsoleClear08Your infrastructure, your rulesDeployment choices
Run it your way.
Use a managed Kubernetes path, register your own Ubuntu VM, or create an app-only preview under the same state and approval model.
Managed Kubernetes
PERCO runs your product on a cluster it manages for you.Import a cluster or bootstrap k3s, then reconcile tenant workloads with server-side apply.
Tenant namespacesDesired-state reconcileExisting cluster import
Bring your VM
Run everything on a server you already own.Register an Ubuntu host, bootstrap the PERCO VM Agent, and inspect readiness before deployment.
Customer-owned hostAgent health checkApp and service deploys
Branch preview
Try changes in a safe copy before they reach production.Create an isolated app preview, attach evidence, and keep promotion behind explicit gates.
App-only child previewEncrypted environmentDestroy or promote
09The payoff
Guided PERCO demo
Proof you can use.
PulseBoard is the guided example: one request becomes a complete product with accounts, data, billing, private services, a domain, and verification evidence.
PulseBoardRoadmap · Ideas · ChangelogLive
Ship better
products, together.
Collect feedback, share roadmaps, and launch with a complete stack.
PassedA user can create an account and sign in.
PassedA signed-in user can submit feedback.
PassedA second user can vote on that feedback.
PassedA workspace can open the Pro checkout flow.
17Export roadmap to CSVIn review · 5 commentsIn review
9Email digest for followersQueued · 1 commentQueued