Integrations
Connect Rhlahto what you already run.
Integration is a governance problem before it is a technical one. Rhlah models providers, credentials, scopes and retries centrally so a connection is never an unaudited side door.
Capabilities
What this engine doesand what it does not.
Each capability below carries its real status. Anything marked planned is modelled in the platform and not yet operating.
Partner API
A read API over your own records, authenticated with scoped, revocable keys and rate limited per organisation.
API keys & scopes
Issue, scope, expire and revoke keys from inside your account, with per-key usage recorded.
AI gateway
Model access for copilots and drafting, governed by budgets and recorded run by run.
Webhooks
Signature verification and retry rules are modelled; inbound delivery is not yet operating.
Payments
Manual and bank transfer are recorded today. Online capture providers are not yet connected.
Communication providers
Email, SMS and messaging channels are modelled end to end; no provider is dispatching yet.
Accounting
Ledger and invoice structures are export-ready; no accounting connector is built.
Travel & supplier systems
Supplier and inventory models exist; external system connections are declared, not built.
Seventeen providers are declared in the integration registry. Declaring a provider is not the same as connecting it, and each one carries its real state in the product and on this page.
Connected by design
Nothing here works alone.
This engine is authoritative for its own domain and reads everything else from the engine that owns it.
API keys
Issued, scoped and revoked from inside the subscriber account.
Audit
Key usage and integration activity recorded per organisation.
Entitlements
Integration capability follows the organisation's plan.
Engines
Every integration writes through an owning engine, never straight to a table.
Ready to run your business differently?
See how Rhlah can fit your Hajj & Umrah operation.