What it is

portal-backend is the main backend microservice for NRW.Desk, a collaboration portal developed by Information und Technik Nordrhein-Westfalen (IT.NRW) for the German state of North

Teams can evaluate portal-backend within its category while keeping the implementation, license, and repository signals visible. Confirm the official documentation against your exact workflow before treating it as a production dependency.

Categories: Content & Collaboration
EU domains: Collaboration Office
EU catalogue: Open CodeStandalone/BackendBeta
Tags: collaboration office web standalone/backend beta eu-oss
Built with: See repository architecture

Who it’s for — and when to skip it

Knowledge teams

Use it when collaborative content should remain exportable and under your control.

Skip if required editing, permissions, or migration features are missing.

Community operators

Consider it when customization and transparent moderation workflows matter.

Skip if your team cannot run community safety and support operations.

Distributed teams

Evaluate it when shared content and communication need an open deployment path.

Skip if realtime scale or mobile experience is not proven for your use case.

Strengths and trade-offs

Why teams consider it

user dashboard personalization

widget grid layout management

system-wide time-bounded notifications

Source code and BSD-3-Clause license are visible before adoption

Repository metrics are available for independent review

What to validate

A public repository does not automatically guarantee a documented self-hosting path

GitHub popularity is not a security, quality, or product-fit guarantee

The BSD-3-Clause license still needs review against your distribution and commercial model

Support quality, migration effort, and production hardening vary by project

Capabilities and stack fit

01user dashboard personalization

02widget grid layout management

03system-wide time-bounded notifications

04JWT-based authentication and role-based authorization

Catalog metadata supports discovery, not installation. Verify supported versions, dependencies, deployment topology, and production requirements in the official repository.

Guides for portal-backend

No project-specific guide is published yet.

Use the learning library to find a guide by technology, category, or difficulty.

Browse guides

Approved community reviews

No approved review signal yet.

We do not display synthetic testimonials or ratings without sufficient moderated data.

Before you adopt it

01
Read the license and confirm it fits your intended use and distribution model.
02
Review recent commits, open issues, releases, and the maintainer response pattern.
03
Run a small proof of concept with representative data, users, and integrations.
04
Confirm whether an official deployment or self-hosting guide exists.
05
Document an export or migration path before storing critical data.

portal-backend