Platform architecture
The parts you only notice when they are missing.
An outbox for events, a job queue, provider adapters, a document service, a notification service, analytics and an audit trail.
The Clix platform is built on an event outbox, a background job queue, provider adapters for external services, a document service, a notification service, an analytics layer and an audit trail. These are the components that make integrations retryable, notifications deliverable and every change attributable.
Events that survive a failure
An outbox means an event is recorded in the same transaction as the change that caused it, then delivered separately. A webhook that fails does not lose the event, and a provider that is down does not roll back the work.
- Event outbox written transactionally
- Background job queue with retries
- Delivery independent of the request
- Failures visible rather than silent
Clix interface shown with sample workspace data
One adapter per provider
Portals, messaging providers, calendars and document services each sit behind an adapter, so adding a destination is a new adapter rather than a change spread through the application.
- Provider adapters with a common contract
- Document service
- Notification service
- Automation service
- 1
- 2
- 3
- 4
- 5
- 6
Everything attributable
An audit trail and an analytics layer run underneath the product, so the question of who changed what, and when, always has an answer.
- Audit trail on records
- Analytics layer
- Job visibility
- Tenant scoping throughout
Clix interface shown with sample workspace data
More of the platform
Further reading
Your brokerage. One operating system.
Start running your real estate business on Clix.
1 month free · No credit card required · $10/user/month