Company

The team behind Palma.

Enterprise software and security people who have run this playbook before — now building the governance layer that lets everyone's agents do real work.

  • Patrick Eden — CEO & Co-founder

    Patrick Eden

    CEO & Co-founder

    Patrick spent his entire career building and scaling solutions for enterprise, previously as a co-founder of an infrastructure monitoring company that exited to Cisco in 2021 with Fortune 100 customers.

    With both a master's in CS and Business Management, Patrick spent most of his career working in highly technical verticals — Kubernetes monitoring and application performance — while volunteering as a board member for the World Economic Forum.

    MCP is profoundly enabling the investment many organisations have already made in AI, and letting them scale their use of it to new levels.
    Connect on LinkedIn
  • Julian Kolbe — CTO & Co-founder

    Julian Kolbe

    CTO & Co-founder

    Julian is a hands-on technical leader with over a decade of experience building secure, scalable systems for Europe's fintech and automotive companies. He has architected financial platforms processing billions in transaction value alongside elaborate automotive systems.

    With extensive experience in regulated environments, Julian understands the importance of compliance, security and reliability in enterprise AI — and is currently focused on building Palma's core infrastructure.

    The intersection of AI and enterprise systems requires a fundamentally different approach to security and reliability. We're building to meet those standards from day one.

Careers

We're hiring.

Palma is remote-first, so you can work from anywhere. We're currently hiring across marketing, product design, sales and platform engineering — join an international team in one of the newest and most consequential areas of enterprise technology.

See open roles

Common Questions

Quick answers about Palma.ai's enterprise MCP platform

What is Palma.ai in one sentence?

Palma.ai is the enterprise governance layer for MCP — it gives every person and agent a single governed connector carrying the tools and Skills they're entitled to, enforces policies on the actual arguments of a call, pauses high-risk actions for approval, and records everything in a tamper-evident audit trail.

What does MCP governance mean?

Deciding which person may use which tool, with which arguments, with whose approval — and being able to prove it afterwards. MCP itself covers how a client authenticates to a server and how a tool is described and called; it does not decide which person may use which tool, hold a risky call for a human, or keep the record an auditor asks for. Palma adds that layer: one governed connector per person, assigned by identity-provider group, carrying the tools and Skills they are entitled to into whichever assistant they already use.

Does my team have to set up MCP servers themselves?

No. Connectors are assigned by IdP group through Entra or Okta, so a joiner gets theirs on day one and a leaver loses it the moment the group changes. Every MCP server your team approves arrives through that same connector — no per-user install, no config files, no credentials sitting on a laptop.

What's a Skill, and why does it matter?

A tool is a verb — "send an email". A Skill is the playbook that tells an agent when and how to use the verbs it already has: how your team actually closes the books, runs an incident review, or qualifies a lead. Skills are versioned, scanned before they're served, and scoped like any other piece of enterprise software — so your best operator's process reaches everyone else's agent.

Does it work with the AI clients we already use?

Yes — everything is served over MCP, so the same connector, Skills and policies follow the person into whichever assistant they open, whether that's Claude, ChatGPT, Copilot, Cursor or something else. Switching tools doesn't mean re-approving, re-installing or re-auditing anything.

How do we prove what an agent actually did?

Every tool call is attributed to the person it was done for, the agent that did it, and the application it ran in — with the arguments, result, duration and cost. The audit trail is tamper-evident and verifiable offline with your own key, so your auditor doesn't have to take our word for it, and it streams to the SIEM you already run.

How is Palma.ai deployed — SaaS, on-prem, VPC?

Palma.ai is designed for enterprise environments: typically VPC or on-prem, including fully air-gapped, depending on your regulatory and security needs. The MCP layer and governance plane run on your infrastructure, so sensitive business data doesn't have to move into multi-tenant SaaS. We can also host it for you if you prefer.

View all questions →