Customer Portal

Public development preview

Build your portal, layer by layer.

Start with authentication, organizations, administration, and a dashboard. Add business capabilities as independent Nuxt layers.

Get started Try the demo GitHub

Nuxt Customer Portal is open source under the MIT License. Read compatibility and release status.

The extension modelNuxt 4
  1. 01

    Headless core

    Sessions, organizations, authorization, database access, and shared server adapters.

  2. 02

    Feature registry

    Layers register navigation, module menus, surfaces, dashboard widgets, and role policies without host edits.

  3. 03

    Business layers

    Each feature owns its UI, API, translations, tests, and PostgreSQL schema.

A working week, end to end.

Timesheets and invoices are used in real Customer Portal deployments. The module covers the complete path from workspace configuration to a paid invoice—not a disconnected feature demo.

  1. 01

    Configure

    Set clients, projects, activities, rates, suppliers, and approval rules.

  2. 02

    Record

    Enter a working week, use timers, submit time, and correct rejected entries.

  3. 03

    Approve

    Move weeks through internal review, client approval, and disputes.

  4. 04

    Invoice

    Create drafts from approved time, deliver PDFs, send reminders, and register payments.

Core stays stable. Features own their work.

The host composes capabilities. It does not need to know their implementation details.

Core
Owns headless authentication, organization context, authorization helpers, shared adapters, and the feature contract.
Registry
Combines installed feature definitions into navigation, module menus, dashboard widgets, and role-aware capabilities.
Feature layer
Owns one coherent business capability, including routes, types, policies, translations, migrations, and tests.
Understand feature layers Read the feature contract

Help shape the portal.

You do not need to start with a large pull request. A precise documentation correction, a failing authorization test, or a focused layer proposal can move the project forward.

Contribution guide
  1. 01Improve the documentationCorrect behavior, add an example, or make a workflow easier to follow.
  2. 02Create a feature layerBuild a portable module against the public core contracts.
  3. 03Propose a moduleShape a reusable capability with maintainers before investing in implementation.

Technology

One Nuxt service and one PostgreSQL database.