Portal

Business Operating Platform

I am building a platform that connects people, processes, data, approvals, integrations, automations and governed agents around shared business objects.

View earlier public reference

Dashboard with synthetic data from the earlier public Portal architecture. — HISTORICAL REFERENCEVisual direction of the earlier public version.The current multi-tenant foundation remains private and in development.

Current stateDevelopment and pre-pilot revalidation

TechnologiesReact · TypeScript · FastAPI · PostgreSQL · Alembic · Redis/Valkey · S3

ArchitectureModular monolith · tenant/RLS · Action Envelope · outbox

VISUAL REFERENCE

From the earlier architecture to the new foundation

These screens belong to the earlier public version and help show the domains and journeys I am reorganizing.

Kanban from the earlier public Portal reference. — HISTORICAL REFERENCEOperations and tracking.

Procurement module from the earlier public reference. — HISTORICAL REFERENCEProcurement and sourcing.

Approval center from the earlier public reference. — HISTORICAL REFERENCEApprovals and governance.

What I have implemented

Tenancy and RLS in the first capability pack, versioned Action Envelopes, approvals tied to content versions, timeline, auditing, outbox, RFQs, offers and supplier comparison.

What still requires validation

The current head is under technical revalidation. Internal pilot, real external effects, scale and commercial operation are not presented as complete.

Problem I want to solve

A business operation often starts in conversation or email, moves through separate spreadsheets and systems, receives approval outside the flow and ends with fragmented history.

What I am building

A multi-tenant kernel with organizations, people, roles, objects, relationships, timeline, auditing, files, governed actions, approvals, observable integrations and capability packs.

How I organized the architecture

React and TypeScript on the frontend; FastAPI and PostgreSQL on the backend; Alembic migrations; tenant/RLS isolation; transactional outbox; workers; and n8n as an external executor through APIs rather than the primary data source.

Current state

Procurement was implemented and previously exercised in sandbox.
Approvals are tied to the content version and hash, allowing material changes to invalidate earlier decisions.
The current head is being revalidated before the internal pilot is defined.

Public reference

The public repository preserves an earlier architecture and does not represent the complete current private foundation.

Next step

Complete revalidation, define the pilot process and users, integrate a real source with reconciliation and measure adoption, time, errors and support.

Portal is described by the real state of each part: specified, implemented, tested, exercised and user-validated are not treated as synonyms.

View earlier public architecture

Next projectCentral ISO

Contact