Openselfservice
Open Self Service (O2S) is an open-source development kit for building composable, future-proof customer self-service portals with API-agnostic architecture that allows you to swap backends without breaking the frontend.
- Author
O2sdev- Updated
Live preview
Live Preview
Interact with the actual deployed template — every section, every interaction, no mockups.
openselfservice.com
Open in a new tab (opens in a new tab)Loading preview…
About
About OpenSelfService
Maintained by Hycom, this framework combines Next.js for the frontend, NestJS for an API harmonization server, TypeScript for type safety, shadcn/ui components, and Tailwind CSS to create flexible customer portals that compose experiences by combining multiple backend capabilities from different sources. The architecture features headless and API-first design allowing any backend to be plugged in, composable backend capabilities where you mix services from different providers, pre-built integrations including StrapiCMS for content management, Auth.js for authentication, Redis for caching, and Algolia for search, extensible UI components and API integration layers, and modular design enabling easy customization without vendor lock-in. Unlike monolithic customer portal solutions that tie you to specific backends and limit flexibility, O2S treats backends as interchangeable building blocks, allowing enterprises to integrate their existing CMS, IAM, CRM, ERP, and other systems without rebuilding the entire frontend when backend providers change.
This approach is invaluable for enterprises building customer portals that need to integrate with multiple legacy systems, organizations wanting to avoid vendor lock-in by maintaining backend flexibility, teams managing complex architectures with services from multiple providers, companies planning to migrate backends over time without disrupting customer experience, and developers who need a production-ready portal foundation with modern UX patterns. The framework demonstrates how to build API-agnostic frontends with proper abstraction layers, integrate multiple backend services through a unified harmonization layer, implement pre-built integrations while maintaining composability, design scalable customer portal architectures, and future-proof applications against backend technology changes. Open Self Service makes building sophisticated customer portals accessible while ensuring long-term flexibility and maintainability.
Get started
Free, open source, and ready to ship.
Clone the repo, install dependencies, and start customising. OpenSelfService is free and open source: its license is in the repository.
- Clone the OpenSelfService repository from GitHub.
- Run
npm installorpnpm installto install all required packages. - Run
npm run devto start the development server and begin customizing. - Check the repository’s README and license before you ship.
Terminal
$ git clone https://github.com/o2sdev/openselfservice $ cd openselfservice $ npm install $ npm run dev
Included in Pro
More Templates
Hand-built premium templates from shadcn.io — production-ready and bundled in Pro.
- Solarisshadcn.io/demos/solaris
Pro - Reframe Labsshadcn.io/demos/reframe
Pro - Spheruleshadcn.io/demos/spherule
Pro - Maxshadcn.io/demos/max
Pro - Zel Designsshadcn.io/demos/zel
Pro - Areteshadcn.io/demos/arete
Pro - Lightboxshadcn.io/demos/lightbox
Pro - Chatlyshadcn.io/demos/chatly
Pro
Every template, every block. One Pro plan unlocks all 14, with 6,000+ blocks and MCP for your AI editor.
Get ProMore like this
More Next.js templates
Open source Next.js templates like OpenSelfService, those with the most in common first.
Pricing
Every premium template, with Pro
All 14 premium templates come with every Pro plan, with 6,000+ blocks and the MCP server. Pick the seats you need.
4.9/5 out of 5 · 150+ reviewsfrom 150+ founders and developers.
- Secure checkout via Stripe
- Code lives in your repo
- Keep what you've shipped if you cancel
- License terms
FAQ
Frequently asked questions
Everything you need to know before you ship with OpenSelfService.
Open Self Service (O2S) is an open-source development kit for building composable, future-proof customer self-service portals with API-agnostic architecture that allows you to swap backends without breaking the frontend. It is an open source template in the shadcn.io collection of 215.
OpenSelfService is made by O2sdev, an independent developer; shadcn.io lists it but did not make it. O2sdev has 1 template in the collection, and the author's page lists them.
The listing tags OpenSelfService with NestJS, Next.js, React and Strapi. Those are its categories, not a dependency list: the exact packages and versions are in the repository's package.json.
Yes. The OpenSelfService page embeds its live demo from openselfservice.com, and links to it so you can open the real deployment before you clone.
The OpenSelfService listing was last updated on October 8, 2025. That date is the listing's, not the repository's: check the repository's commits for recent activity.
Clone the repository (git clone https://github.com/o2sdev/openselfservice), then follow the README. The OpenSelfService page shows the usual steps and a terminal block with the commands to copy.
Install dependencies with npm install or pnpm install, then run npm run dev. The README in the OpenSelfService repository says which package manager and environment variables it needs.
No. OpenSelfService is cloned from its own GitHub repository, so shadcn.io isn't involved. Browsing the page and its live demo need no account either; Pro adds the premium templates, the blocks and the MCP server.
OpenSelfService is tagged Next.js, so it deploys wherever a Next.js app does, such as Vercel, a Node.js server or a container. Its README may add steps for its own services.
The OpenSelfService listing doesn't record a license. Check the LICENSE file in its repository (https://github.com/o2sdev/openselfservice), and ask the author if there isn't one.
That depends on OpenSelfService's license in its repository, which shadcn.io does not set. Read the LICENSE file before you use it in a client or paid project, and ask the author if it is unclear.
Attribution follows OpenSelfService's license. Many permissive licenses ask you to keep the copyright notice and license text in your copy; its LICENSE file says exactly what.
No. The Pro license covers shadcn.io's own Pro code, blocks and premium templates. OpenSelfService is the author's project, under the terms in its repository.
O2sdev supports OpenSelfService, through its GitHub repository: read the docs, open an issue or look for discussions. shadcn.io does not maintain it.
Yes. Once you clone it, OpenSelfService is your own code: change the theme, add pages and connect your backend. It uses shadcn/ui, so you can also add more components the same way.
Yes. Components are free with a free account and the blocks are in Pro; both are copied into your project with the shadcn CLI. Check that OpenSelfService uses Tailwind CSS and the shadcn/ui setup (a components.json) before you add them, and pick the base library your project already uses.
Yes, with Pro. The shadcn.io MCP server's search_templates tool finds templates by what they are, and returns each one's repository and live demo, so your editor can set up OpenSelfService for you. Your files stay on your machine.
The collection has 151 other open source Next.js templates like OpenSelfService, shown at the foot of its page with the ones sharing most categories first. All of them are at /template/category/nextjs.
O2sdev has no other templates in the collection.
Yes. The 14 premium templates (Solaris, Reframe Labs, Spherule and Max and more) are built by shadcn.io and come with every Pro plan, if you want maintained code with a design file.
4.9 out of 5 from 150+ developers
Ship your next site this weekend
14 premium templates, 6,000+ blocks and MCP in every Pro plan. OpenSelfService and the other 214 open source templates stay free.
Get Pro