cd ..

[ project / 01 ] · Corporate SSO Ecosystem

OneHub.

One login, four apps: the platform that digitalized an entire company's internal operations.

private codebase
Node.jsTypeScriptReactPostgreSQLDockerGitHub ActionsTurborepo

in action

The interface

Core Platform· OneHub login
1 / 12
OneHub login
expand

click image to expand fullscreen

about the project

OneHub is the platform I architected, built and shipped as lead developer at Wissensforte: a corporate SSO ecosystem of 4 apps running across 9 production services, each with its own Node.js backend and React front end. Before it existed, the company managed time tracking and financial reconciliation through Excel spreadsheets stored in SharePoint: constant risk of versioning conflicts, lost entries and file chaos. OneHub replaced all of that, saving around 29 hours per month and becoming the foundation for structuring processes across the entire company.

The foundation is a centralized authentication service (SSO, 2FA, session management, rate limiting and token lifecycle control), plus a cross-service RBAC system with a full admin panel, so management controls permissions without developer intervention. On top of it run four business apps: the OneHub portal (company dashboard), ClockWorks (time tracking and PDF payroll reports), FortePay (expense reimbursements) and Orion (support ticketing).

Every service follows the same standardized architecture (Controller, Service, Repository, validation, security middleware) and lives in a Turborepo monorepo where lint, typecheck and test run in parallel across workspaces with build cache, and shared packages are always compiled before their consumers run tests.

The test suite uses characterization testing against a real HTTP contract: tests spin up an actual Express app and assert status codes and response bodies (the exact contract the frontends depend on). This made a large middleware migration (moving to a shared @onehub/auth package) safe to ship: every behavioural change was explicit and verified before merging. On the deploy side, GitHub Actions pushes to a self-managed VPS via SSH: the deploy script runs git reset --hard + git clean while preserving .env, so the server is always in exact sync with the repository without wiping local secrets.

project.meta

type
Corporate SSO Ecosystem
stack
Node.js · TypeScript · React · PostgreSQL · Docker · GitHub Actions · Turborepo
source
private

in their words

In terms of process, it helped us by 200%. Without it, we'd be managing everything in Excel spreadsheets in SharePoint — versioning issues, lost entries, file confusion. I'd spend at least 5 hours a month just on that. On the financial side, it saved me roughly 29 hours a month on hour-closing, reconciliation and accounts payable. But the biggest gain is one you can't put a price on: OneHub was the foundation for structuring processes across the entire company.

Managing Partner

Wissensforte Technologies

what it does

Key features

01

Centralized auth with SSO and 2FA

One authentication service for every internal app, handling sessions, rate limiting and full token lifecycle control.

02

Cross-service RBAC

Roles, permissions and per-app access managed from an admin panel. No developer needed to grant access.

03

Four apps in production

OneHub portal, ClockWorks, FortePay and Orion: independent Node.js + React services covering the company's full internal operation.

04

Turborepo monorepo + HTTP contract tests

Parallel lint/typecheck/test pipeline with build cache. Tests assert real HTTP responses (not implementation details), making refactors safe to ship.