Managed execution
- Isolated environments
- Repository integrations
- Hosted browser testing
- Deployment verification
WebMCPify Cloud · In development
Agent readiness without the local setup.
Run Core in an isolated workspace matched to your production environment, verify against the deployment, and keep new pull requests agent-ready.
IN DEVELOPMENT Cloud is not generally available. Repository and production access will stay limited to permissions a customer explicitly grants.
MANAGED WORKSPACEISOLATED
New pull request→Agent-readiness run
01Buildmatched env02Browserreal test03Verifyevidence04Proposereviewable PR
No code or environment access outside the granted boundary.
Hosted workflow
From repository connection to continuous evidence.
Cloud is designed to host the Core workflow without removing its checkpoints. Isolation, human review, and independent verification remain part of the product.
- 01
Connect an authorized repository
- 02
Choose a branch and matching environment
- 03
Run discovery in an isolated workspace
- 04
Review proposed capabilities and changes
- 05
Test with a real browser agent
- 06
Independently verify outcomes
- 07
Deploy approved changes
- 08
Monitor capability health
- 09
Detect semantic drift
- 10
Propose reviewable repairs
Planned capability groups
Operate the capability layer.
Repeatable environments, health signals, and controlled improvement in one managed workflow.
Capability operations
- Health monitoring
- Optional agent analytics
- Failure and latency signals
- Compatibility alerts
Controlled improvement
- Approval-controlled repair
- Evidence history
- Drift detection
- Reviewable recommendations
Security model
Managed does not mean unrestricted.
Repository access, credentials, deployments, and browser sessions remain scoped to the environment a team explicitly connects.
01Per-run isolated workspaces
02Scoped repository and environment access
03Secrets kept out of capability arguments
04Human approval before consequential changes
05Independent post-deployment verification
06Evidence and audit history
Optional agent gateway
A control plane for agent traffic.
Cloud is planned as a defensive boundary between agent requests and approved backend actions—not a promise of absolute security.
Identity & access+
Agent identities, authentication, authorization, and fine-grained policies.
Trust signals+
Layered inspection around agent and capability activity without exposing the internal detection model.
Action accountability+
Optional records of scoped visits, tool calls, outcomes, and verification evidence.
Backend connection+
Policy-controlled links to APIs and databases without exposing ungranted systems.
Monitoring & alerts+
Capability health, unusual behavior, failures, latency, and customer-selected notifications.
PR continuity+
With a monthly subscription, evaluate each new repository PR and propose capabilities, fixes, and fixtures for human review.
Analytics and monitoring are optional. Customers choose the scope, access, and retention; private arguments and secrets are excluded by design.