JavaScript
Use the maintained JavaScript binding in browser applications and supported JavaScript runtimes.
Read official guideLanguages and environments
Authorization that fits your stack.
Cedarling brings one Cedar policy model into the languages and environments developers already use—from browser apps and mobile clients to backend services, gateways, databases, and sidecars.
Keep decisions local, integration familiar, and enforcement close to the action.
Language bindings
Use the language you already ship.
Embed Cedarling through a maintained binding while keeping the policy model consistent across services and clients.
Python
Add local Cedar policy decisions to Python services, automation, and data workflows.
Guide planned
Rust
Embed the native Cedarling engine where ownership, performance, and tight lifecycle control matter.
Guide planned
Go
Bring Cedarling into Go services, gateways, and infrastructure-oriented applications.
Guide planned
Java
Integrate Cedarling into JVM services and established enterprise application stacks.
Guide planned
Kotlin
Use Cedarling from Kotlin services and shared mobile-oriented code.
Guide planned
Swift
Bring local Cedar authorization into Swift applications across Apple platforms.
Guide planned
C
Link Cedarling into native, embedded, or cross-language systems through its C binding.
Guide plannedDeployment surfaces
Put policy where the action happens.
Choose an in-process binding or a sidecar based on the trust boundary your application must enforce.
Browser
Evaluate policy beside browser interactions for responsive experiences, while keeping server-owned resources enforced by the server.
Guide plannedBackend services
Keep authorization beside the business operation that owns the protected data or side effect.
Guide plannedAndroid
Embed Cedarling in Android applications through the maintained mobile binding.
Guide plannediOS
Embed Cedarling in iOS applications through the maintained Swift and UniFFI path.
Guide plannedAPI gateways
Evaluate Cedar policies at an API boundary before requests reach protected upstream services.
Guide plannedDatabases and search
Place policy decisions close to PostgreSQL or OpenSearch-backed data access.
Guide plannedSidecar
Expose Cedarling beside applications that cannot or should not embed a language binding.
Guide plannedOne policy language
One policy language across every boundary.
Reuse the same Cedar concepts while each application supplies its own policy store, request facts, and enforcement code.
Local decisions
Avoid a network hop for each authorization request.
Portable policy model
Keep Cedar policies independent from framework-specific authorization branches.
Explicit trust
Use validated tokens or identity established by the host application.
Application-owned enforcement
Keep the final protected operation inside the system that owns it.
Start with the maintained integration guidance.
Read the official JavaScript guide, or use the ecosystem references to explore the source and other maintained bindings.