Your system of record
stays where it is.
Etci is built on top of your existing architecture; it does not replace it. Data ownership stays with your organisation, permission scope is inherited, every access is written to the audit trail.
Book a DemoThe systems your team
already works in.
Etci does not replace these systems, it operates on top of them. Once connected, automations and AI agents act inside them within the same permission scope.
You pick the system and approve the requested permissions on the provider's own screen. The connection is live in the same session. No password reaches Etci, and access cannot exceed the approving user's own permissions.
1 approval · 0 lines of code
Systems outside the list connect with a single authenticated call. Endpoints support POST and GET, events are delivered by signed webhook. No glue code left to maintain.
Authorization: Bearer <api_key>
Running a system built specifically for your organisation?
Request an integration reviewWire up your own connector
with a single call.
Resource-oriented REST endpoints, signed webhook delivery, queryable event history. Authentication is a Bearer key; endpoints support POST and GET.
Permissions, audit trail
and key management.
The integration layer inherits your existing permission and compliance policy.
Permission scope
A connection cannot exceed the access limits of the user who approved it.
Audit trail
Which user did what in which system, timestamped and queryable.
Key lifecycle
A key is shown once, stored in isolation, revoked individually.
Signature verification
TLS in transit, encryption at rest; webhook requests are signed.
Let's start with the architecture you have.
We review your systems, data flows and permission model together, then build the integration plan around them.
Book a Demo