Curate-Me By Role
Different teams look at the same platform from very different angles. This page maps the product to the jobs people inside a company actually have.
Executive / Founder
What they usually care about
- are we shipping AI safely enough?
- are we overspending on model usage?
- do we have operator visibility if something goes wrong?
- can we tell a credible story to enterprise buyers?
What Curate-Me gives them
- a clearer control surface for AI operations
- budget and usage visibility
- a stronger governance and compliance story
- fewer internal tools stitched together by hand
Most relevant areas
- dashboard cost and health surfaces
- approvals
- policy controls
- role-based reporting
Engineering Lead / Platform Lead
What they usually care about
- standardizing model access
- policy enforcement across teams
- reducing ad hoc provider integrations
- safe execution for agents and workflows
What Curate-Me gives them
- one gateway integration point
- centralized controls for cost, model access, and approvals
- managed runner infrastructure
- logs and health signals operators can actually use
Most relevant areas
Product Manager / AI Ops
What they usually care about
- which flows are healthy?
- which tasks need approvals?
- where are teams getting blocked?
- what is usage trending toward?
What Curate-Me gives them
- dashboard visibility into request logs, approvals, and operational health
- easier handoff between engineering and operations
- a place to reason about changes without reading backend logs first
Most relevant areas
- dashboard overview
- approval queues
- cost tracking
- gateway logs
Security / Compliance
What they usually care about
- secrets and PII leaving the system
- model access boundaries
- auditability
- evidence during investigations
What Curate-Me gives them
- request checks before provider calls
- model governance and allowlists
- approval gates for risky workflows
- request and execution visibility for audit trails
Most relevant areas
- gateway governance chain
- approvals
- audit logs
- runner security docs
Finance / Procurement
What they usually care about
- what are we spending?
- who is driving that spend?
- can we set hard limits?
- do we need separate vendors for gateway, runtime, and observability?
What Curate-Me gives them
- clearer AI spend attribution
- daily and monthly budget controls
- one platform covering multiple tool categories
- dashboards that make usage easier to explain
Most relevant areas
- cost tracking
- billing
- usage and budget controls
Support / Customer Success
What they usually care about
- what happened in a failed run?
- can we explain to a customer why something was blocked or approved?
- do we have a trace or request ID to work from?
What Curate-Me gives them
- gateway request logs
- request IDs and health views
- runner activity surfaces
- operator-friendly dashboards instead of raw infrastructure logs
Most relevant areas
- dashboard overview
- gateway logs
- system health
- runner activity
Application Developer
What they usually care about
- how little do I need to change?
- does my SDK still work?
- how do I debug failures?
- how do I get access to runners when I need more than an API call?
What Curate-Me gives them
- base URL swap instead of a full rewrite
- SDKs and quickstarts
- governed request path with response metadata
- runner APIs and templates for more advanced workflows
Most relevant areas
A Simple Adoption Pattern
Base URL swap, first governed request, first logs.
1. Developer starts with the gatewayKeys, costs, approvals, and health become visible.
2. Ops and PM use the dashboardExecution moves into managed environments with stronger controls.
3. Platform team adds runnersThe company can now explain how AI work is controlled and observed.
4. Leadership gets clearer governance