Joyst

JOYST FOR PLATFORM TEAMS

AI platform engineering. Govern skills and MCP servers beside your IDP.

AI platform engineering deserves the same care as the rest of your platform. Your team already runs a developer portal, yet ad hoc AI installs still slip through: unapproved skills, undocumented MCP servers and no clear owner. Joyst sits beside Backstage, Port and similar IDPs. It holds approved skills and a private list of approved MCP servers, with permissions and an audit trail.

dash.joyst.app
Platform team governance of AI tools in Joyst

THE PROBLEM

Ad-hoc AI installs need an allow-list

  • Installs live in personal configs

    People connect MCP servers and drop skills into their own setups. The platform team loses sight of them, and onboarding and security reviews get harder.

  • No clear owner

    When skills and MCP connections live in Slack threads and laptop configs, nobody owns the approved list for engineering.

  • Approved set for engineering

    Platform teams need approved skills and MCP servers, with permissions and an audit trail, so installs no longer rely on word of mouth.

WHAT YOU GOVERN

Approved skills and MCP allow-list

  • Skills registry for engineering

    Publish and version the skills your organisation may use, so teams do not keep a separate copy for each vendor.

  • Private MCP catalogue

    Document tools, keep an approved list and give agents approved servers only, not ad hoc personal connections.

  • Permissions and audit

    View, use and manage rights, folder permissions and a central audit trail, all under AI governance.

  • Secrets for agents

    The secrets vault holds the keys your AI tools and agents use. Agents refer to them by name, and nobody pastes them into chat. Infrastructure secrets stay in your existing secrets manager.

BESIDE YOUR IDP

Beside Backstage and Port, not instead of them

  • Keep your developer portal

    Backstage, Port and similar IDPs catalogue software services. That job stays with your portal. Joyst does not replace an IDP.

  • Add a catalogue for AI

    Joyst catalogues skills, prompts, MCP servers, secrets and agents beside the portal. Each does its own job.

  • Keep what works

    Platform teams with an IDP still see ad hoc AI installs. Joyst sits beside Backstage and Port and keeps the approved list for AI tools.

  • Private catalogue only

    Skills and approved MCP servers owned by your organisation. Not a marketplace, not a public skill store and not a replacement for your developer portal.

RELATED

Keep exploring.

  • Use cases hub

    How platform teams and agencies use a private AI catalogue.

    Open
  • Agencies

    Shared libraries with client-safe secrets.

    Open
  • Skills registry

    Manage, version and move skills across AI tools.

    Open
  • MCP catalogue

    Connect, document and approve MCP servers.

    Open
  • Beside your IDP

    How Joyst works beside your IDP.

    Open
  • Secrets vault

    Keys kept out of model context.

    Open
  • Agents

    Package skills, prompts, MCP servers and secrets into reusable setups.

    Open
  • Roll out AI across the organisation

    Roll out approved AI with owners, permissions and an audit trail.

    Open

Platform teams FAQ

Yes, if you need a catalogue for AI. Backstage catalogues software. Joyst catalogues skills, prompts, MCP servers, secrets and agents. Use both.

No. It is not an IDP and does not replace service catalogues or scorecards.

Yes. You get a private catalogue, documentation, an approved list, permissions and an audit trail.

No. The catalogue is private to your organisation.

Under AI governance: view, use and manage rights, folders, groups and the audit trail.

Book a platform demo, or start free.

Create an organisation account and bring skills, prompts, MCP servers, secrets and agents into one private catalogue.

  • Private to your organisation
  • Draft, then publish
  • Limited open beta
Start free beta