FAQs
Speedle looks awesome! Who is it for?
Speedle is an open source project for access management. You can embed it in your system as long as access control is required, such that you don’t have to hard code authorization policies in your code.
Does the world need one more policy engine?
Well, please spend 15 minutes on Quick Start steps. Then you will have the answer. Why not give a try? :-)
How do I contribute?
Please refer to contribution guide
What does the future hold for Speedle? What’s the plan?
We will maintain Speedle as an open source project, fix bugs, add more features…
How is it different from OPA, Kubernetes RBAC, Istio RBAC?
Long story short: They all target to authorization/access control. Kubernetes RBAC and Istio RBAC focus on the authorization issues in Kubernetes/Istio system respectively, while Speedle and OPA are general purpose authorization solution. There are also a few other general purpose authorization solutions, like Casbin and Ladon. You may try them out yourself and see
- Is the product user-friendly? These products all offer policy definition language. Try to create a policy and pick up the one you like
- Is the product fast enough? i.e. how long does it take to evaluate an authorization request?
- Is the product is scalable enough?
- Is the supported policy model flexible enough?
Please tell us your choice.
Why does Speedle have no built-in auth mechanisms?
Speedle focuses on authorization field. It doesn’t cover authentication functionality.
How do I plug in my own backend store?
Please refer to Pluggable Storage
How do I plug in my own token assertor?
Plase refer to token assertor
Can’t see the answer you’re looking for?
Try our Slack workspace #speedleproject
Visit Slack channel →