Devpost
Participate in our public hackathons
Devpost for Teams
Access your company's private hackathons
Grow your developer ecosystem and promote your platform
Drive innovation, collaboration, and retention within your organization
By use case
Blog
Insights into hackathon planning and participation
Customer stories
Inspiration from peers and other industry leaders
Planning guides
Best practices for planning online and in-person hackathons
Webinars & events
Upcoming events and on-demand recordings
Help desk
Common questions and support documentation
I build developer tooling, and the plumbing agents run on. Mostly TypeScript
The agent behind the library help desk for official letters people can't read. It checks every date and amount against the page, and on a folded photo it left out the 7 facts it couldn't find.
A phone-call agent for on-call: your stack calls YOU when production breaks, talks the incident through, and runs the fix you authorize out loud.
Dependency bumps scored 0 to 100 by a fixed, published rubric, then acted on: safe ones become pull requests, risky ones get held with a migration plan. Nothing merges on its own.
An incident-response agent whose memory you can audit: a receipt on every recall, and UNKNOWN when it couldn't check.
What breaks if this ships? Blast Radar walks your DataHub lineage over MCP, ranks which downstream assets a change actually endangers, and writes the verdict back into the graph.
