What authorization models does Permit.io support?
Permit.io supports Role-Based Access Control (RBAC), Attribute-Based Access Control (ABAC), and Relationship-Based Access Control (ReBAC), allowing for dynamic and granular permission management.
How does Permit.io handle policy definition and deployment?
Policies can be defined using a no-code UI editor or generated as transparent policy-as-code based on OPA's Rego or AWS' Cedar. These policies are managed as code in Git and controlled via a simple API, supporting a full GitOps CI/CD pipeline for automated deployments.
What is the hybrid deployment model and its benefits?
The hybrid deployment model ensures that all authorization decisions are made on the user's side with zero latency. This allows sensitive data to be used for authorization decisions without ever leaving the user's VPC/network, enhancing security and ensuring continuous availability even if Permit.io's cloud service experiences issues.
Can Permit.io integrate with existing systems and identity providers?
Yes, Permit.io offers extensive integration capabilities, including language SDKs for Node.js, Python, Go, Java, C#, React, and Ruby. It also integrates with API Gateways, Proxies, Databases, GraphQL, and JWT-based Identity/Authentication Providers.
What compliance standards does Permit.io meet?
Permit.io is compliant with major standards such as HIPAA, SOC2, GDPR, and CCPA, providing robust security and data privacy assurances for various industry requirements.
What are Monthly Active Users (MAU) in Permit.io's pricing model?
MAU refers to the number of unique identities (users or services) that your application authorizes monthly. The pricing tiers are structured based on these MAU counts, along with the number of tenants and environments.