Design direction

INTEGRATIONS

Integrations built through controlled interfaces

RLX Gate prefers versioned adapters and explicit secret boundaries over embedding credentials in browser configuration.

Last reviewed

The operating problem

Integration catalogs become security and maintenance liabilities when every connector receives unrestricted network, payload, or secret access.

The intended control surface

This capability is part of the reviewed product architecture, not a decorative console module.

  • Versioned provider interfaces
  • Scoped secret references
  • Health and capability metadata
  • Audited configuration and revocation

What exists today

Envoy, ClamAV, SQLite, Cloudflare Tunnel, GHCR, GitHub OIDC signing, WebAuthn, and application JWT/OIDC verification are integrated. SMTP, object storage, event bus, administrator federation, and external analytics adapters remain future work.

Work with the implementation team

Reallexi is accepting architecture conversations with teams whose requirements can shape this production slice. An inquiry does not imply that an unshipped feature is available.

Frequently asked questions

Is this capability generally available?

No. The page describes a reviewed implementation direction. The current capability boundary is stated above and in the public changelog.

Can Reallexi evaluate our requirements?

Yes. Use the enterprise inquiry form without including credentials, private payloads, or regulated data.

NEXT STEP

Shape the requirements before implementation.

Talk to ReallexiRequest platform access