Solutions by Role

Role-based control for the AI-powered organization — engineers ship faster, security teams stay compliant, and leaders monitor every token spent.

Role-based paths into one intelligence runtime: Teams for shared governance, Agent Builders for MCP/API embedding, Individuals for human scenes without MCP JSON on the page. Same five capabilities and seven primitives underneath—not seven separate products.

For Teams & Enterprise

Team intelligence governance — visibility with enforcement.

Production agents need one intelligence runtime, not seven re-implemented primitives per project. SmartGate gives teams shared caps, audit, and the same five capabilities (Research, Context, Memory, Control, Pipeline) whether humans use the Web or builders wire MCP.

Team-scoped token caps, MCP rate limits per API key, and optional L2 hard stop when monthly limits bite.
Activity logs and budget guard for FinOps, security, and platform reviews — gateway counterfactual, not host-model invoices.
Role-based guides below (from our content index) for engineering, security, and operations leaders.

Start with audit and traffic features, then wire Cursor or internal agents to the same gateway URL your dashboards already meter.

Audit & compliance features See pricing

Role guides

FinOps Lead: Own the AI Bill — Measure, Alert, Report

For the FinOps lead who owns the AI bill: a per-team quota percentage, 80% and 100% alerts, avoided-token dollars, and audit rows summed into a spend report you can sign off on.

SmartGate MCP for Research and Decisions: A Personal Workflow

How an individual uses SmartGate MCP for research and decisions: one server entry in the assistant you already use, then search, fetch, deduplication, context and memory on every question.

What Solutions by Role actually maps to

SmartGate is the intelligence layer between AI and the world: an MCP-native algorithmic gateway, not an LLM proxy or chat assistant. Solutions pages organize that runtime by who owns the problem—teams that need shared caps and audit, agent builders who need one Streamable HTTP surface, and individuals who want research-grade outcomes without MCP JSON on the marketing page.

Under every tab the same five capabilities run: Research, Context, Memory, Control, and Pipeline—powered by seven smart_* primitives. Humans enter through Web scenes; builders enter through MCP/API. Both share team-scoped metering, Activity Logs, and fair-use rate limits on Free and Playground that soft-fail with HTTP 429 when bursts exceed entitlements.

Use Teams when FinOps and security need visibility with enforcement. Use Agent Builders when you refuse to rebuild fetch, dedup, compression, budget guard, memory, and orchestration per agent. Use Individuals when the product promise is Smart Research, Smart Decision, Smart Knowledge, or Smart Intelligence—outcomes first, protocol later.

These pages do not invent customer logos, fixed savings percentages, or concurrent capacity figures. Est. USD saved in the product is a gateway counterfactual for comparing tool paths, not a restatement of your host LLM invoice. Pair Solutions with Features (Token Control, Traffic Customs, Audit) and Docs when you are ready to wire Connect JSON.

How to choose a starting path

If you already run Cursor, Claude Desktop, Windsurf, or OpenClaw, open Agent Builders and copy Dashboard Connect for your host. If you are evaluating personal research before any MCP setup, start with Research and decisions, then the homepage proof URL cleanup, then a signed-in Playground preset. If you are buying for a shared workspace, read Teams copy, then Pricing and Audit features, then invite roles from Docs Teams.

Role guides published to our content index appear under the Teams tab as they ship. Until then, the static panels and feature links are the durable path: one gateway origin, team isolation, and audited tool traffic.