Trust
Trust & governance
Shynvo is built for teams that get reviewed — whether by security, finance, or their own future selves at 3 a.m. These are the control surfaces that make automation defensible.
Control surfaces
Each block below maps to a signed-in route. Read the full narrative on the platform overview.
Audit trail
Operational events — API keys, billing webhooks, approvals, automation activity — are designed to land in one append-oriented log you can export and walk through with auditors.
Audit log →Approvals
High-impact automation waits for an explicit approval record before execution. The queue is a first-class route, not a side channel.
Approvals →Connectors
Optional HTTP backends for reasoning, robot-style automation, and health checks. Nothing runs against your stack until you configure endpoints and credentials.
Connectors →API access & keys
Scripts and integrations authenticate with scoped keys. Keys are created and rotated from Settings; usage flows through the same-origin API surface documented in the reference.
API keys →
Execution posture
The console surfaces an execution mode callout on automations and approvals: dry-run first when available, approvals for gated work, and audit visibility for what changed. Defaults favor proof over speed.
Rate limits & abuse resistance
Public and sensitive routes use lightweight in-memory rate limiting where configured, so incidental traffic spikes do not overwhelm your deployment. Tune limits in your hosting layer as traffic grows.
Operators should expect
- Explicit authentication for user APIs and alert ingest
- Append-oriented audit when the database and service role are configured
- Clear separation between session demo mode and production-backed workspaces