Architecture
How Xevrion is built.
Where each part runs, how every request is checked, and the rules that keep your data safe and the service reliable.
14 days free No payment details No sales calls
Verified company fact From the production deployment.
Layers
From the edge to the database.
Edge
- WebsitesStatic pages served from Cloudflare's global network, with strict security headers.
- TunnelThe only way in to the platform: an encrypted tunnel, with no ports open on the server.
- AI bridgeA private, token-protected Worker that runs the AI model on Cloudflare Workers AI.
Gateway
- Platform gatewayEvery request enters here: sign-in, organisation and role checks, plans and limits, rate limits and routing.
- Customer appThe portal your team uses, served by the gateway with a strict content security policy.
Systems
- Customer CareCustomer emails and requests, health, renewals and expansion.
- AutomationsThe library of 40 automations, Design my automation, checks, dry runs and versions.
- SecurityThe score, the checks, your answers, findings and the fix plan.
- Business mapThe map of people, work, tools, data, money and customers, and what-ifs.
- Automated WorkRoutines, work items, documents, finance and procurement.
- Valuable InsightsData, key numbers, forecasts, what-ifs, learning and memory.
Shared services
- Governance, security and reliabilityIdentity, secrets, approvals, audit, error budgets and recovery.
- Integrations and communicationsConnectors, email, webhooks, retries and circuit breakers per customer.
- Automation and agent controlRuns workflows and agents within policy, with hand-offs to people.
- Business data and knowledgeThe shared business model, approved knowledge and document retention.
- Customer service managementPortfolio, renewals and value across all customers.
- Finance and performanceRevenue, cost, cash and SaaS metrics.
- Quality, analytics and optimisationExperiments, control charts and delivery performance.
- Executive controlObjectives, decisions and company health.
Data
- PostgreSQLEach service owns its own database, with reviewed, checksummed migrations.
- BackupsA full backup and a tagged rollback image before every upgrade.
Engineering rules
Six rules every service follows.
Bounded services
Each system owns its own data and database. Services talk through the gateway with their own credentials, never sharing tables.
IsolationDeny by default
Security checks that cannot complete refuse rather than allow.
SafetyIdempotent writes
Every change in another system carries a key, so retries never apply twice; unclear outcomes are reconciled.
SafetyPer-customer circuit breakers
If one customer's tool fails, only that customer's calls to it pause; nobody else is affected.
ReliabilityError budgets
Each service tracks its reliability targets and alerts when the budget is burning too fast.
ReliabilityChecksummed migrations
Database changes are reviewed, recorded and verified before every release.
Change
Built to be trusted with real work.
Read the security details, or start with the whole platform from £995 a month.
14 days free No payment details No sales calls