Agent-native operations for real customer apps

Weppa Cloud gives MSPs and agencies a governed control plane where agents can diagnose, deploy, validate and roll back production apps.

  • Every mutation starts as an operation_run
  • Risk tiers route the right human approvals
  • GitOps and adapters apply only allowlisted changes
  • Evidence and rollback are part of the product
PR opened

main -> staging

Open
Preview built

Isolated URL ready

Ready
Approval

Policy checks passed

Approved
Deploy

Published to production

Live
Rollback

Target version recorded

Safe

Diagnose

Agents inspect apps through bounded tools instead of shelling into customer infrastructure.

Learn more

Approve

High-risk changes wait for explicit approval with plan hash, scope and rollback context.

Learn more

Evidence

Operation runs record events, artifacts, smoke results and final GO or NO-GO decisions.

Learn more

Rollback

Productized rollback keeps recovery tied to the same governed path as deploy.

Learn more

Built for agencies that cannot guess in production

The important change is not another dashboard. It is letting agents touch real apps only through governed operations.
Weppa product spine Agent-native control plane
GitOps remains the declarative source, but the operator experience starts with operation_run and evidence.
Weppa architecture GitOps boundary
Static sites are the first packaged topology: low runtime cost, high governance value and repeatable rollback.
Weppa Sites Catalog topology

Questions operators ask before launch

Answers stay short because the template should make the governed path obvious.

Is Weppa a PaaS or an operations control plane?

Weppa is an agent-native operations control plane. The PaaS substrate exists to make governed operations repeatable.

Where does GitOps live?

GitOps lives in GitHub as the declarative source of truth. The Control Plane creates governed changes and Flux applies them.

Can GitHub Actions operate production?

No. Actions can run CI only. Productive mutations go through operation_run, worker, evidence and rollback.

Why start with static sites?

Static sites prove the catalog topology with low runtime cost while keeping preview, deploy and rollback fully governed.

Operate the next change through Weppa

The beta is focused on real governed operations: diagnose, deploy, validate and roll back with evidence.

Request beta access

Start with a governed operation

Share the app, site or migration you want an agent to operate. The first useful output should be evidence.