Find your way in.
Three situations. One control plane.
LumenFlow governs AI agent work wherever policy, approvals, and evidence are part of the job. Pick the one closest to what you’re doing.
Regulated enterprise:
govern agents across the organisation
External agents, SDK-connected runtimes, and internal tools all report to the same policy layer. Approval routing, evidence export, and fleet visibility from one control plane.
- Policy enforcement and approval routing across every connected agent
- Evidence and attestation exports that support your compliance and audit readiness
AI engineering:
control AI-driven software delivery
Scope gates, co-change rules, and release approvals keep AI-written changes safe to ship, with every decision captured from commit to production.
- Release gates and rollback approvals before code reaches production
- A record of every gate decision, approver, and rollback — exportable for review
Private compute:
operate AI inside infrastructure you control
Bring your own model-provider key, connect your own machines, or run on dedicated infrastructure — the same policy, evidence, and audit trail wherever the compute runs.
- Bring your own key or connect your own hardware as a governed node
- The same evidence chain whether a run happens in the cloud or on your machine
Try six concrete scenarios on the hosted sandbox.
Every playground run is a real anonymous Sidekick session in LumenFlow’s hosted sandbox, with sandbox-only sample data. Ask for work, watch the approvals and receipts appear live, and keep the whole thing connector-free.
Incident Triage
Checkout is failing for a third of users. Coordinate the fix.
An incident is live and Sidekick has to read the situation, plan the next steps, ask for approval on a rollback, send the update, and leave proof of every choice.
- Role
- Incident commander
- Connectors
- Status page, On-call chat
- Approval boundary
- A production rollback waits for the incident commander or release captain.
- Evidence
- An incident record showing impact, the rollback decision, who approved it, and the next checkpoint.
Release Shipping
A release is ready, but staging caught a problem. Should it ship?
Sidekick reads the release state, runs the gates, asks the release captain to sign off on the rollback posture, sends the update, and files the record — so the team knows whether to ship and why.
- Role
- Release captain
- Connectors
- Release gates, Deploy
- Approval boundary
- A production deploy waits for the release captain to sign the preflight and rollback plan.
- Evidence
- A release record with the gate results, the deploy decision, the rollback reference, who approved, and what was sent.
Customer Escalation
An overnight report failed. The customer wants an answer in 20 minutes.
An enterprise customer escalated, the proposed credit crosses your sign-off limit, and the reply is due now. Sidekick drafts the response, routes the credit for approval, sends the update, and files the record.
- Role
- Account owner
- Connectors
- Support desk, Billing
- Approval boundary
- A credit above the account owner's limit waits for the duty manager.
- Evidence
- A customer record with the impact, the proposed credit, who approved, and the outbound message.
Restaurant Host Desk
A regular just walked in early. Service is tight. Make it work.
Service is busy, a VIP regular needs a table now, and the only way to seat them on time means a comp the host can't approve alone. Sidekick proposes the move, asks the manager, sends the guest messages, and logs the shift.
- Role
- Host
- Connectors
- Reservations, Waitlist
- Approval boundary
- A comp or table move waits for the manager.
- Evidence
- A shift log with the exception, who approved, and how it was resolved.
Hotel Guest Ops
Five guest requests, two of them need a fee waiver. Handle them.
A hotel has a queue of guest requests — early check-in, late checkout, a fee waiver, a dietary note. Sidekick handles the easy ones, asks an operator before waiving fees, and sends the guest the right reply.
- Role
- Front desk
- Connectors
- Property system, Guest messages
- Approval boundary
- A fee waiver waits for an operator.
- Evidence
- A case file with the request, the policy reference, the operator's decision, and the outbound message.
Portfolio Ops
An issue is hitting six properties at once. One decision. One message.
A regional issue is unfolding across multiple properties. Sidekick combines the picture, proposes a single response, asks the regional lead to approve it, and sends every property the same playbook.
- Role
- Portfolio operator
- Connectors
- Property alerts, Guest messages
- Approval boundary
- A cross-property exception waits for the regional lead.
- Evidence
- A portfolio record tying the property impacts, the approvals, and the operator-facing actions together.
Ready to govern your AI work?
Start free with one workspace. Define your policy boundary and see governance in action.