4-Portal Architecture — The Right Data to the Right People
Separate environments for manufacturers, suppliers, market surveillance verifiers, and platform administrators. Role-based data isolation by design — not by configuration.
Company Portal
Manufacturers, importers, authorised representatives
Create and manage product passports. Upload documents for AI extraction. Monitor compliance scores. Manage supply chain data. Publish passports and generate QR codes. Full audit trail of every action.
Supplier Portal
Upstream component and raw material suppliers
OTP-authenticated access — no account creation needed. Suppliers see only the data requests directed to them. Enter component data, upload certifications, respond to due diligence questionnaires. Your product data stays invisible.
Verifier Portal
Market surveillance authorities
Verification queue for submitted passports. Full access to passport data at the market surveillance tier. Verification status tracking and audit trail. Designed for the workflow described in Battery Regulation Article 77.
Superadmin Portal
Platform operators and white-label partners
Manage companies, subscriptions, and module access. Monitor platform health. Configure branding for white-label deployments. Entity registry and communications management.
Data isolation by design
Portal isolation is not a permission layer added on top of a shared database view. Each portal is a separate application environment with its own routing, its own middleware, and row-level security policies at the database level.
- Row-level security (RLS) on every database table
- Company-scoped queries — no cross-tenant data leakage
- Separate JWT session management per portal
- Audit logging on all data mutations across all portals
- Role-based middleware enforced at the server layer, not the UI