Architecture & domains
How Transparent fits together as a platform: domains, cross-cutting systems, and illustrative flows. Pair this with module pages and deep dives for feature-level detail.
What Transparent is
An end-to-end language-service-provider (LSP) operations platform: sales and CRM, project/job/task delivery, vendor and resource management, finance (client and vendor), quality, master data, security, integrations (SAP, TMS/Memsource, FreshSales, partner feeds, cloud files, mobile APIs), and heavy automation via crons and queues.
Core domains (how parts work together)
- CRM & commercial — Leads, accounts, contacts, opportunities, campaigns, forecasts feed projects and jobs and set billing behaviour (price books, PO culture, account teams).
- Delivery — Projects contain jobs; jobs break into tasks; tasks link to TMS/files, evaluations, and eventually vendor invoices. Auto-planning and resource strategies assign talent from calendars and RFR.
- Talent — Resource profiles, availability, evaluations, and account teams constrain who can be assigned and how they are paid.
- Finance — POs and jobs roll into client invoices; tasks roll into vendor invoices; payments and SAP sync reconcile externally.
- Platform — Row-level security, configurable grids/lists, audit logs, messaging on records, dynamic reports, multi-company identities per login.
Cross-cutting capabilities
- Security engine — Status/event/role-driven access; privileges rebuilt by background jobs.
- Configurable UI — List templates, view templates, Gridmap, exports, scheduled reports.
- Integrations — SAP, Memsource, Welocalize/Junction/Moravia, FreshSales, Cognito, Moodle, Google Drive/ownCloud, email command parser, AWS SQS.
- Channels — Web UI, mobile APIs, webhooks, scheduled crons.
High-level flow (diagram)
Illustrative overview — revise the diagram when the architecture narrative changes.
flowchart LR
CRM[CRM / commercial] --> Projects
Projects --> Jobs
Jobs --> Tasks
Tasks --> TMS[TMS / files]
Tasks --> Talent[Talent / RFR]
Tasks --> VInv[Vendor invoices]
Jobs --> CInv[Client invoices]
Jobs --> PO[PO management]
Risk themes (for revamp planning)
- Large monolithic controllers and raw SQL in places — regression and security review cost.
- Background jobs critical to security and finance — need observability and runbooks.
- Secrets and token handling in legacy integrations — rotate and externalise during modernisation.
For drill-down on specific areas, use the deep dives linked from module cards and the catalogue.