The Team
Building developer tools developers actually enjoy using.
Behind AlleForge is a small team obsessed with developer experience, performance, and thoughtful product design. Every feature is built by engineers who use the platform every day.
Dhaval Patel
Founder
Founder
Meet the Builder Behind AlleForge
AlleForge started with one simple belief: API development should happen where developers already work — inside the browser.
I spent years watching developers fight with tools locked to machines, broken mocks, and documentation written once and forgotten. Every team had a different setup. Nothing stayed in sync.
The browser solved this for every other category. API tooling was the obvious gap. AlleForge is the workspace I wanted — open a tab, build requests, write tests, generate mocks, collaborate in real time. No installs. Every feature we ship, we use ourselves the same week it lands.
“Great developer tools don’t add more features.
They remove more friction.”
Our Team
Creative Minds
Meet Patel
Senior Software Engineer
Vishwa Sonar
Senior Software Engineer
Poojan Sakhreliya
Backend Engineer
Ahmed Kazi
Senior Software Engineer
Riddhi Prajapati
QA Engineer
Om Patel
Frontend Engineer
Our Philosophy
The principles behind every feature
Developer First
Every decision starts with the developer experience.
Build With Purpose
Every feature solves a real workflow problem.
Quality Over Quantity
Ship fewer features, but make each exceptional.
Continuous Improvement
Small team, short feedback loop — issues get looked at the same week, not the same quarter.
How We Build
A tight loop, run on repeat
No big-bang launches. Every feature moves through the same six stages, over and over.
- 01
Research
Talk to developers, read the friction, find the real problem.
- 02
Prototype
Sketch the workflow before writing production code.
- 03
Build
Ship a working slice, not a mockup.
- 04
Test
Use it ourselves, on our own workspace, first.
- 05
Ship
Release small, release often, watch closely.
- 06
Improve
Feedback loops back into the next research cycle.
- 01
Research
Talk to developers, read the friction, find the real problem.
- 02
Prototype
Sketch the workflow before writing production code.
- 03
Build
Ship a working slice, not a mockup.
- 04
Test
Use it ourselves, on our own workspace, first.
- 05
Ship
Release small, release often, watch closely.
- 06
Improve
Feedback loops back into the next research cycle.
Team Values
What we hold each other to
Ownership
Everyone owns the outcome of what they ship, not just the code they write.
Transparency
Decisions, roadmaps, and setbacks are shared openly, inside and out.
Craftsmanship
The details nobody asked for are usually the ones that matter most.
Curiosity
We stay students of the problem, not just builders of the solution.
Speed
Small releases beat big ones. Momentum compounds.
Reliability
Developers trust AlleForge with real workflows — that trust is earned every release.
Powered by Collaboration
Everyone sees the same board
Pull requests, reviews, tests, and deploys all live on one board — nobody needs a status meeting to know where something stands.
Pull Request
#482 · 3 files changed
Design Review
Approved, no revisions
Code Review
2 of 2 approvals
API Testing
48 assertions passed
Deployment
v2.4.0 · live
Completed Tasks
12 shipped this week
Comments
“LGTM, ship it 🚀”
How We Work
Small team, no compromises
Projects built
Developers helped
API requests tested
Countries reached
Open source contributions
Ready to build better
developer tools?
Join a team that ships fast, listens closely, and sweats the details other tools skip — or just come build alongside us.