Skip to content
NR.Niels Rigter

Dashboard and customer portal built for a hosting platform

Customers needed to manage hosting, domains and payments themselves instead of via tickets. A Next.js portal with checkout, integrations and automated delivery, technical narrative without naming the client.

The problem

Manual follow-up of orders and changes did not scale: error-prone, slow and expensive in support.

Customers expected self-service: see status, manage products, pay and trigger technical actions without waiting.

Approach

  1. 01

    Portal around daily jobs

    Dashboard focused on what customers really do: overview, order and manage. Not ten half-finished modules.

  2. 02

    Integrations that hold up

    Domains, hosting providers, payments and webhooks as reliable flows with clear error handling.

  3. 03

    Permissions and data in order

    Clear roles for customer versus admin, with a stable database as the source of truth.

  4. 04

    Automate delivery

    From paid order to working service with status in the portal, so support is not the bottleneck.

Technology

Next.jsDrizzleNeonAPI integrationsPayment providers

Result

  • Self-service for core processes instead of email chains.
  • Less support load on routine questions, more time for exceptions.
  • A base to add products without rebuilding the portal.

Screenshots

Stylised UI mocks. Not real client screenshots.

  • Customer dashboard

  • Products & domains

  • Checkout & status

Performance

Indicative example at delivery. Not a live measurement of a client site.

Performance

94

Accessibility

98

Best practices

100

SEO

100

Load time: ~0.9s

No. Value sits in concrete flows (hosting, domains, delivery), not charts alone.

← All projects