Custom portals require an Enterprise plan and a self-hosted deployment. Reach out to your account team to scope one.
Features
Authoring flow
The custom front end doesn’t affect how content gets written. Maintain content with the editor or a local Git-based workflow. Every change flows through your repository’s review process with a full audit trail, and publishing triggers builds that update the portal automatically. Content changes do not require a front-end deploy.Architecture
The custom presentation layer integrates with the self-hosted Mintlify platform for content, search, and personalization; your API gateway for applications, subscriptions, and support; and your identity provider for authentication. The custom presentation layer and Mintlify platform run inside your network boundary, using your cluster, data stores, and observability stack, with no third-party egress. Your downstream systems of record remain unchanged; the portal accesses them through your existing APIs.How the engagement runs
1
Scope and design
Your account team maps the portal surfaces, your design system, and the backend APIs the portal consumes, and agrees on an integration contract with your platform team.
2
Public surfaces first
The engagement typically implements your design system and public content surfaces first, so you can validate the experience against your existing portal before cutover.
3
Authenticated surfaces
Sign-in, credential management, subscriptions, and other logged-in experiences follow, integrated with your identity provider and backend APIs.
4
Search, personalization, and AI
Login-aware search and server-side personalization complete the core experience. Optional AI features remain disabled until your security or AI governance team approves them.
Next steps
Talk to your account team
Scope a custom portal engagement and plan your launch.
Self-host
The deployment foundation a custom portal runs on.