Plans & Seats

Note: This is mock/placeholder content for demonstration purposes.

SC Sentinel plans are a flat price per tier, with each tier including a set number of seats. A seat covers one developer who will use security context through their AI assistant. Seats are shared across Claude, Cursor, Copilot, and Windsurf — the license is account-level, not tool-level.

Starter

The Starter plan is designed for small teams and individual security champions who want to bring policy enforcement into their own workflow before rolling it out broadly.

• Up to 5 seats
• Full access to the SC Sentinel rule library
• Standard security context responses
• Email support
• 30-day audit log retention

Pro

Pro is for teams actively enforcing security standards across a development organisation.

• Up to 50 seats
• Everything in Starter
• Custom rules — define your own keyword and term rules in the dashboard, each with a severity, served alongside the standard library
• Team-scoped policy overrides — suppress or escalate specific rules for your organisation without forking the standard library
• 90-day audit log retention
• Priority support with a 1-business-day response SLA

Enterprise

Enterprise is for organisations that need custom contract terms, SSO, or on-premise deployment.

• Unlimited seats
• Everything in Pro
• SAML/OIDC single sign-on
• Private MCP server deployment (your infrastructure, your network)
• Custom audit log retention and export
• Dedicated support channel
• SLA negotiated per contract

Contact sales@sc-demo.xyz to discuss Enterprise pricing and deployment options.

Rate limits

Each plan includes a request rate limit on the SC Sentinel MCP endpoint, enforced as a token bucket — a steady refill per minute plus a short burst allowance:

• Free (no active license): 60 requests/minute, burst 20
• Starter: 300 requests/minute, burst 50
• Pro: 1,200 requests/minute, burst 100
• Enterprise: 6,000 requests/minute, burst 300

When the bucket is empty the endpoint returns HTTP 429 with a Retry-After header. Your current limit is shown on the License health card on the MCP Integration page.

Adding and removing seats

Seats are managed from the dashboard under Settings → Team. Inviting a team member consumes one seat; removing them from the team releases it.

The MCP Integration page shows a License health card with your seat usage against your plan's cap. If your team exceeds the cap, the card shows a warning prompting an upgrade — your MCP requests keep working. The same card reports active developers in the last 30 days: the number of distinct developers who used an API key (a shared key counts as one).

Mid-cycle seat additions are prorated to the next billing date. Removing a seat takes effect at the end of the current billing period.