01
Product console
Hosted UI at sovereign.ops / agents.ops with demo seed and read-only sessions. Best for evaluation, training, and stakeholder walkthroughs.
Sign in / demoDocumentation
Intro to Wecrew Ops
A vendor-neutral, multi-tenant, read-only agent operations plane for regulated hybrid infrastructure — what agents are doing, what they may do, and why something broke, with evidence you can take to audit.
- Passports cite identity, budget, and blocked actions
- Self-hosted on your cluster — data stays inside your network
- Console stays strictly read-only
sovereign.ops › docsIntro
On this page
Live surfaces
- Command Centre
- Agent passports
- Investigate
- Govern
Looking to chat with the console? Visit sovereign.ops sign-in or continue without an account for the product demo.
sovereign.ops.wecrew.in
Choose your path
Two ways to use Wecrew Ops
Same product language — hosted evaluation or self-hosted residency.
02
Self-hosted estate
Same application image on your Kind / K3s cluster behind Traefik or ingress. Best for regulated estates that must keep agent ops data on-prem.
Deploy guideGetting started
Recommended path for new operators
Follow these steps to go from zero to a working Wecrew Ops session.
01
Open the console
Sign in or start a demo session. Scope tenant, customer, and environment from the top bar.
Sign in02
Read Command Centre
Fleet health, open incidents, SLA risk, and spend — before any single investigation.
Command Centre03
Trust every passport
Signed identity, autonomy, step and token budgets, blocked actions, orchestration routing.
Agent Registry04
Investigate with evidence
Incident workspace, hash-verified artefacts, and RCA packages stay linked.
Sample incident05
Govern with an audit trail
Approvals, policy, SOC signals, and immutable audit — still read-only.
Approvals
Operate
Build an operations practice around agents
Entry points your team will use after the intro — demo, deploy, or talk to us.
Product demo
Walk the live console with seeded Nordic Federated Bank production scope — no cluster required.
Launch demoSelf-hosted deploy
Run the same UI on your Kind / K3s estate. Data stays inside your network.
Deploy guideContact
Talk about regulated estates, residency, and rollout with the Wecrew Ops team.
support@wecrew.in
Capabilities
What operators use Wecrew Ops for
Observability, passports, governance, and investigation — not a dashboard bolted onto a chat window.
Language of operations
Summarize fleet state, answer operator questions, and surface passport, budget, and incident context in one plane.
Evidence & visuals
Host/IP/application identity, timelines, graphs, and hash-verified artefacts that stand up in audit.
Agent governance
Passports, orchestration routing, SOC, approvals, and policy — without production write from the UI.
Support
Questions about residency, rollout, or the console?
Talk to the Wecrew Ops team, or return to the product overview for solutions and security posture.
Rajkumar Madhu
Runs on your infrastructure · Read-only by design · Evidence cites its sources