Frontend
Next.js app router for onboarding, catalog management, registration review, and operations dashboards.
Architecture
Recommended system shape
Keep the platform modular: one canonical publishing model inside, partner-specific adapters outside.
Publishing API
Dedicated backend service for works, parties, splits, registrations, notifications, and audit records.
Workflow Engine
Background jobs for outbound CMO notifications, inbound acknowledgements, retries, and exception queues.
Data Layer
PostgreSQL for canonical rights data plus object storage for import files, statements, and evidence.
Backend recommendation
Use a dedicated API service and queue-backed workflow layer.
A separate backend should own publishing records, validation rules, and integration adapters. Workflow processing should handle retries, scheduled syncs, inbound acknowledgements, and manual review routing.
Integration rule
Every CMO gets an adapter, not custom core tables.
Build transport-specific connectors for API, SFTP, CSV, XML, or portal-driven flows while keeping one internal data contract across the product.