Identity & access
Keycloak federation, Authelia operator flows, and SSO patterns that plug into your workforce IdP.
CITRICLOUD
Connect identity, delivery, and tools without losing secure platform defaults.
Integrations should reinforce controls — not bypass them.
CITRICLOUD is designed to sit under your product: GitOps for delivery, Traefik at the edge, identity for operators and tenants, and marketplace apps for common SaaS needs.
Whether you federate an IdP or install a catalog app, the same isolation and TLS defaults apply.
Categories
Six surfaces that cover most production SaaS glue work.
Keycloak federation, Authelia operator flows, and SSO patterns that plug into your workforce IdP.
Declarative delivery that fits GitHub, GitLab, and review-based promotion into production.
Metrics, logs, and traces wired for operators — plus status for customer-facing transparency.
Curated SaaS installs into isolated namespaces with TLS and identity included.
Traefik ingress, middleware chains, and hostname-level controls for every public surface.
Webhooks, APIs, and operator runbooks so your tools can drive environments safely.
Clear docs, reviewable changes, and support that knows the stack.
Integrations are only useful if they stay operable at 3am. We favor patterns that are observable, reversible, and attributable through GitOps.
Keycloak
Federation and tenant identity
Authelia
2FA forward-auth for operators
Traefik
Edge routing and middleware
Kubernetes
Workload runtime and isolation
GitOps
Reviewable production changes
Marketplace
One-click curated apps
Step 1
Identity, edge, marketplace, or observability — start where your product feels friction.
Step 2
Use documented patterns so credentials and scopes stay least-privilege.
Step 3
Keep status, docs, and support in the loop as the integration becomes production-critical.
Yes. Contact Partners or Support with your use case — we prioritize patterns that help multiple customers.
Marketplace apps are installable workloads. Integrations are how external tools and identity providers connect to the platform.
Start in Documentation for API references and runbooks. Enterprise customers can request deeper architecture sessions.