AI automation for every project. Governed by your MCP gateway.

Let AI agents automate work in Jira, Confluence, GitHub, Slack and your data. Least-privilege access per project, and a full audit trail on your own servers.

Everything your AI tools ask for passes through one gate.

Claude, Cursor, an internal chatbot — whatever your team uses, it no longer holds the keys to Jira, GitHub or Slack. It asks Vordix, and Vordix decides. Every request, every time, written down.

  • Checks who is calling
  • Checks what they may do
  • Applies your data rules
  • Records the call
How every request is checked
A monolithic gate at dusk, every light stream converging to pass through its single lit opening.

Agents that move your projects forward.

Vordix is not tied to one kind of project. Wherever work runs on Jira, Trello, Notion, Confluence, GitHub, Slack, mail or your data, agents can take on tasks at every stage, and every stage keeps its own controls.

AI agent at work
01 / 04

Plan

What agents do

Groom the backlog, plan sprints and milestones, keep boards current.

What stays under control

Only the projects and boards you approve. Updating and moving, yes; deleting only if you switch it on.

Read more

MCP access control at four levels.

Configure which tools an agent can use, which operations it may run, which parameter values are allowed and which response fields it receives. An organisation-wide ceiling limits the permissions each project can grant.

Example: let an agent read Jira issues in project MOB, deny delete operations and redact email addresses from the response.

See how it applies
Tool-level permission Jira: enabled
Vordix governs every level
01ToolJira connector enabled
02Operationread & search only, no delete
03Parameter valuesproject = MOB only
04Response fieldsemails & names redacted

Names and addresses never reach the model.

Before an answer leaves Vordix, sensitive fields are masked or removed. The agent still gets everything it needs to do the work, and nothing it has no business seeing.

How sensitive data is handled
What Jira returns
summary
Payment retry fails on 402
assignee
Martina Kellner
reporter
Jonas Weber
What the agent sees
summary
Payment retry fails on 402
assignee
user_4471
email
removed
reporter
user_1180
Data streams tracing a route through an alpine valley at dusk, past lit villages.

Your data stays where you are.

Vordix runs on your own servers, as a single deployment you install and control. We never see your data, because we are never in the path. Built in Austria, for teams that want AI in everyday use and governance that holds.

Why self-hosted matters

Not a connector list. A governance layer per tool.

  • Jira

    Locked to approved projects; assignee & reporter emails masked.

  • GitHub

    Scoped to approved repos; merges and writes can require approval.

  • Confluence

    Limited to approved spaces; author names masked.

  • Notion

    Limited to approved databases & pages; author names masked.

  • Slack

    Approved channels only; agent messages treated as inert text.

  • Discord

    Approved channels only; member details masked.

  • MS Teams

    Approved channels only; agent messages treated as inert text.

  • Trello

    Scoped to approved boards; member details masked.

  • Databricks

    No raw SQL; queries are built from approved tables, read-only and row-capped.

  • Web Search

    Domain-allowlisted, read-only; results returned as inert text.

  • Gmail

    Scoped mailboxes; recipient PII redacted per field.

  • Outlook

    Scoped mailboxes; recipient PII redacted per field.

  • Azure DevOps

    Scoped to approved repos and pipelines; write operations fully audited.

Every integration listed here is available today. More are on the way.

MCP gateway questions, answered.

What is Vordix?

Vordix is a self-hosted governance gateway that sits between your people, your AI agents, and the tools they use, including Jira, GitHub, Slack, Databricks and more. Every request is authenticated, scoped to approved operations, rate-limited, and written to an immutable audit log before it ever reaches a tool.

How does Vordix actually work?

Vordix runs as a reverse proxy in front of your tools, reachable over both the Model Context Protocol and a plain REST API. When an agent calls a tool, Vordix verifies the identity behind the key, checks it is allowed that exact operation on that exact resource, applies your data-policy rules to the response, logs the full interaction, and only then returns the result.

How is this different from handing an agent an API key?

A raw API key usually carries the full permissions of the human who created it: whole-account access, with no way to say “this project, these operations, not that field.” Vordix issues a key per identity, scoped to exactly the tools, operations and data each agent needs, so a leaked or misbehaving agent can never reach beyond its mandate.

Is Vordix an MCP gateway?

Yes. Vordix speaks the Model Context Protocol, so any MCP client (Claude, Claude Code, Cursor, VS Code or an internal chat tool) connects to one governed endpoint instead of a dozen raw servers. The same controls apply to a REST API for clients that don’t speak MCP.

How does Vordix improve security and compliance?

It centralizes authentication, authorization and audit in one place. Access is default-deny and least-privilege: tool- and operation-level scoping limits blast radius, field-level data policies mask or redact sensitive values, rate limits and lockouts contain abuse, and every security-relevant action lands in a tamper-evident audit trail your auditors can read.

Where does Vordix run, and who can see our data?

Vordix is self-hosted: it runs entirely on your own infrastructure via Docker Compose. Credentials, traffic and audit logs never leave your network, and integration secrets are never handed back to a client. You stay compliant without trusting a third-party SaaS with access to your tools.

When should we put Vordix in place?

As soon as more than a handful of people or agents touch your tools, or the first time compliance asks “who did what, and could they have done more?” Vordix is built for production-scale AI: per-identity keys, centralized access control and audit-ready logging from day one.

See Vordix on your stack.

Tell us what you’re trying to govern and we’ll walk you through it. The gateway runs on your infrastructure, with no Vordix-operated cloud in the request path.

Every request and every identity, fully under your control.

Prefer email? Write to [email protected]

Please confirm you have read the privacy policy.