The product

    The Sector8 Gate

    Sector8 is the control point between AI systems and the business actions they want to take. Before AI accesses data, issues a refund, updates a system, exports records, changes files, or calls connected tools, Sector8 returns ALLOW or DENY. The agent does not approve itself.

    For technical teams, that means policy-based control over API calls, file operations, shell commands, MCP tools, deployments, and connected systems. Same action. Same policy. Same decision. Every decision creates a record of what was checked and why.

    • refunds
    • exports
    • customer data
    • system updates
    • workflow actions
    • shell
    • filesystem
    • network
    • MCP
    • CI/CD

    How it works

    Propose. Decide. Prove.

    We do not try to govern what the model thinks. We govern what it is allowed to do.

    1

    Propose

    The AI system proposes an action. Your runtime sends that proposed action to Sector8 before it happens. This can include tool calls, API calls, model calls, file operations, handoffs, or workflow actions.

    2

    Decide

    A deterministic policy engine returns ALLOW or DENY. If it cannot allow the action safely, it denies. No model judges another model.

    3

    Prove

    Every decision carries a reason code, decision trace ID, evidence hash, and policy version. Allows are recorded, not just denials.

    How you connect

    Connect Sector8 before AI reaches your systems

    Choose the integration path that fits your AI workflow. Start in shadow mode, record decisions, then turn on enforcement when ready.

    Sector8 is model-agnostic. It works wherever proposed actions can be routed through the gate: APIs, SDKs, agent runtimes, MCP tools, internal copilots, and customer-facing workflows. The control boundary is AI-to-action, not application-to-model.

    REST

    POST /api/v1/evaluate from any runtime. Honour the decision before the side effect starts.

    Python SDK

    sector8-sdk wraps the same evaluate contract.

    TypeScript SDK

    @sector8/sdk wraps the same evaluate contract.

    Claude Code / MCP

    Route governed tool calls through the Sector8 connector. REST evaluate returns ALLOW or DENY. On the MCP connector path, a borderline action can be held for a human; if nobody answers, it is denied. Tools the agent can still call around the connector are not covered.

    Business workflow / API

    Route proposed business actions such as refunds, exports, CRM updates, and account changes through the same evaluate contract.

    Set a client timeout of at least ten seconds so a slow or failed call fails closed instead of executing — that timeout is a safety backstop, not an expected latency. If the gate cannot decide, the action does not run.

    Enterprise controls included

    • Tenant-isolated policy enforcement
    • EU-hosted deployment
    • Encryption in transit and at rest
    • Versioned policy sets, bound per tenant
    • Auditable decision evidence

    Where it matters

    One gate, several action surfaces

    Customer-facing agents

    Control refunds, exports, account changes, CRM updates, customer record access, and other actions that move money or data.

    Internal copilots

    Control access to HR, finance, legal, operational, customer, and knowledge systems before AI acts on sensitive information.

    Coding agents

    Control shell commands, file changes, repository access, deploys, secrets, MCP tools, and CI/CD workflows before they run.

    Public reason codes live on /reason-codes. Branch on the decision, not on a specific code.

    Setup

    Shadow mode first. Enforcement after the report.

    1. 1. Identify the action surface. Coding agents, copilots, or customer-facing tools.
    2. 2. Route proposed actions. SDK, REST, or the Claude Code connector. Only routed tools are governed.
    3. 3. Run shadow mode. Enforcement off. ALLOW and DENY are still recorded.
    4. 4. Turn on selected policies. After you have seen what the agents already tried.
    Sector8 Gate execution control plane with a sample DENY path and evidence fields

    Product UI shown with enforcement enabled. Shadow mode records the same decisions without blocking. Sample path, not a named customer.

    Scope

    Where Sector8 fits

    • Sector8 is not a replacement for SIEM, DLP, content security, or governance programmes.
    • Sector8 supports evidence collection, but does not certify GDPR, HIPAA, or EU AI Act compliance by itself.
    • Sector8 governs actions routed through the gate. Shadow mode helps identify coverage gaps.
    • Classification can inform a decision, but the control point is whether the proposed action is admitted.

    Test the gate before you enforce

    Two weeks. Enforcement off. A report of what your agents already tried. Then you choose which controls to turn on.

    Ecosystem

    Supported by innovation and enterprise ecosystems

    Sector8 is building within recognised innovation and enterprise technology ecosystems across Ireland, Dubai, and the MACH Alliance community.

    Local Enterprise Office logo

    Local Enterprise Office

    Supporting Irish entrepreneurs and early-stage businesses.

    Enterprise Ireland logo

    Enterprise Ireland

    Supporting Irish companies with international growth ambition.

    in5 Innovation Centre Dubai logo

    in5 Innovation Centre Dubai

    Supporting technology startups and innovation in Dubai.

    MACH Alliance logo

    MACH Alliance

    Agent Ecosystem Collaborator, contributing to the conversation around AI agents and composable enterprise architecture.

    Listed organisations reflect Sector8's support, membership, and ecosystem relationships. This does not imply product endorsement unless explicitly stated.