We're thrilled to partner with Permit.io for a brand new DEV challenge focused on reimagining application authorization!
Running through May 4, the Permit.io Authorization Challenge invites you to push the boundaries of what's possible with authorization-as-a-service.
Gone are the days of hardcoding authorization or building complex in-app permissions. With Permit.io's powerful platform, you can manage access control easier than ever β making your applications more secure, flexible, and easier to maintain.
We have three prompts for this challenge with three ways to win from our $3,000 prize pool. Winners also get a very cool custom Permit.io mechanical keyboard. π
Ready to revolutionize the way applications handle permissions? Read on for our prompts!
Our Prompts β¨
Permissions Redefined
Build an application of your choice and implement fine-grained authorization using Permit.io. We strongly encourage you to utilize the Permit CLI. Document your process and guide others through implementing similar solutions.
Permissions Redefined Submission Template
Your submission will be judged primarily on the quality of your documentation (DEV submission post and repository README) but we expect the core functionality of your project to work as well.
AI Access Control
Build an AI application of your choice that includes authorization controls specifically designed for AI (i.e. safeguards for AI actions that require approval workflows, fine-grained controls over what AI agents can access or modify, etc). Document your process and guide others through implementing similar solutions.
AI Access Control Submission Template
Your submission will be judged primarily on the quality of your documentation (DEV submission post and repository README) but we expect the core functionality of your project to work as well.
API-First Authorization
Build an application of your choice that elegantly implements an authorization system that embraces API-first principles and declarative rules using Permit.io.
Avoid generic, boilerplate CRUD apps β weβre looking for thoughtful implementations that demonstrate real-world access control and meaningful architecture. Treat authorization as a core part of your API design, enforced through external policies rather than hardcoded logic. Document your process and guide others through implementing similar solutions.
API-First Authorization Submission Template
Your submission will be judged primarily on the quality of your documentation (DEV submission post and repository README) but we expect the core functionality of your project to work as well.
Judging Criteria
All submissions will be judged on the following:
- Clarity and Quality of Project Development Journey
- Clarity and Quality of Project README (Installation/Tutorials/Guides)
- Functionality and Usability of Application/Tool
- Innovation and Creativity in the Authorization Approach
Prizes
The winner of each prompt will receive..

All valid submissions will receive a completion badge on their DEV profile.
How To Participate
In order to participate, you will need to publish a post using the submission template associated with your selected prompt.
We strongly encourage you to:
- Focus on demonstrating the benefits of externalized authorization vs. traditional approaches as part of your application and/or submission post.
- Deploy a working application
Important notes:
- Please make testing the app as straightforward as possible by providing testing instructions and/or using these admin and user credentials if applicable:
- Admin:
- username:
admin
- password:
2025DEVChallenge
- User:
- username:
newuser
- password:
2025DEVChallenge
- You may use AI to support your process (in fact, one of the prompts requires it!) but AI slop won't win.
- Never include sensitive information like API keys in your submission, codebase, or readme!!!
- Please review our full rules, guidelines, and FAQ page before submitting so you understand our participation guidelines and official contests rules such eligibility requirements.
Need support?
We encourage all participants to join the Permit.io Slack, and here are some resources to help you get started:
Important Dates
- April 23: Permit.io Authorization Challenge begins!
- May 4: Submissions due at 11:59 PM PST
- May 15: Winners Announced
We're excited to see how you'll reimagine authorization with Permit.io! Questions about the challenge? Ask them below.
Good luck and happy coding!
Top comments (18)
Gabriel from Permit.io here, super exciting to see your submissions!
If anything comes up along the way, feel free to reach out to me on our Slack community at: io.permit.io/slack
BTW, there is still a way to win the keyboard by joining one of our launch week Livestreams at: launch.permit.sh
Awesome!!
Will definitely be checking out permit.io!
I had to control access to certain features for users in different groups (subscription plans) on my service before, but I didnβt know something like this existed, so I ended up implementing my own authorization service.
Awesome!
I really need a new mechanical keyboard so bad, but I just don't have the capacity to join rn. Good luck to the hackers!
Go go go the race is on!
Happy coding everyone! π€
Wishing everyone the best of luck, canβt wait to see what you build π»πͺ
I love this! Challenge accepted
That keyboard!!! π
Good luck everyone!
Good luck!
Some comments may only be visible to logged-in visitors. Sign in to view all comments.