JOYST FOR PLATFORM TEAMS
Platform teams — govern skills and MCP servers beside your IDP
Platform and eng-ops teams already run developer portals. Ad-hoc AI installs still slip through: unapproved skills, undocumented MCP servers, and no clear owner. Joyst sits beside Backstage, Port, and similar IDPs as the AI asset layer — approved skills and a private MCP allow-list with permissions and audit.
PLATFORM PAIN
Ad-hoc AI installs need an allow-list
- Installs live in personal configs
Individuals connect MCP servers and drop skills into personal setups. Platform loses visibility; onboarding and security reviews get harder.
- No clear owner for AI assets
When skills and MCP connections live in Slack threads and laptop configs, nobody owns the allow-list for engineering.
- Approved set for engineering
Platform teams need approved skills and MCP servers — with permissions and audit — so installs stop living in tribal knowledge.
WHAT YOU GOVERN
Approved skills and MCP allow-list
- Skills registry for engineering
Publish and version the skills the org may use so teams are not maintaining forks per vendor surface.
- Private MCP catalogue
Document tools, keep an allow-list, and feed agents from approved servers only — not ad-hoc personal connections.
- Permissions and audit
View / use / manage tiers, folder permissions, and a central audit trail under AI governance — not GRC theatre.
- Secrets for agents
Keep client and infra keys in the secrets vault — referenced by agents, not pasted into chats.
POSITIONING
Beside Backstage/Port — not instead
- Keep your developer portal
Backstage, Port, and similar IDPs catalogue software services. That job stays with your portal — Joyst is not an IDP replacement.
- Add the AI asset layer
Joyst catalogues skills, prompts, MCPs, secrets, and agents beside the portal — complementary layers for complementary jobs.
- Not a rip-and-replace pitch
Platform teams already running an IDP still face ad-hoc AI installs. Joyst sits beside Backstage and Port as the allow-list for AI assets.
- Private catalogue only
Org-owned skills and MCP allow-lists — not a marketplace, not a public skill store, and not a developer-portal swap.
Use cases hub
Use cases hubAgencies
AgenciesSkills registry
Skills registryMCP catalog
MCP catalogBeside IDP
Beside IDPSecrets vault
Secrets vaultAgents
AgentsPlatform teams FAQ
Yes if you need an AI asset layer. Backstage catalogues software; Joyst catalogues skills, prompts, MCPs, secrets, and agents. Use both.
No. It is not an IDP and does not replace service catalogs or scorecards.
Yes — private catalogue, documentation, allow-list, and permissions/audit.
No. Private org catalogue only.
Under AI governance: view / use / manage, folders, groups, and audit trail.