Main track
1 winner
Best overall project
MacBook Neo
The strongest product built and shipped over the weekend.
Judged on the idea, the execution, and how Zerops is used.

Registration
Registration takes a minute and it's the only way in. Do it now, and spend the weekend building instead of signing up.
01 / About
Now
Sign in, fill in the registration form, and you're on the list.
Sat, Aug 8
The challenge, the rules, and a live Zerops walkthrough. Watch the stream.
Aug 8–9
Build the product and get it deployed on Zerops. Registration stays open through August 8.
Sun, Aug 9
File your project in the same panel before the deadline.
No planning phase, no slide decks. Forty-eight hours, concept to deployed product.
No fixed tracks, no prescribed categories. Bring whatever fits the idea.
Production-grade infrastructure, not a local demo or a screen recording.
Your application keeps working through judging, not just at launch.
02 / Prizes
One for the best project, one for the best post about it. Every entry is in both.
Main track
1 winner
Best overall project
The strongest product built and shipped over the weekend.
Judged on the idea, the execution, and how Zerops is used.
Social track
1 winner
Top social post
The build post that best shows the work behind the project.
Judged on the clarity of the story, the demo, and its reach.
Credits pool
$5,000
In Zerops credits, split across standout projects that make real use of the platform.
03 / The challenge
Build an application, service, platform, or developer tool, and deploy it on Zerops.
Example project
Illustration only
One way a project could be put together on Zerops. None of it is required, and a single container counts, so take as much or as little of this as your product needs.
Public traffic
Frontend
Static or SSR
API
Any runtime
Private network
Database
Postgres, Mongo…
Cache
Valkey, KeyDB
Workers
Queues, cron
Storage
Object store
What counts as finished
04 / How participation works
Register, build, post, submit. Step three is not optional, and it has a shape.
Takes a minute, and it's the only way in. Do it before you start building.
Make something meaningful, and deploy it on Zerops.
Post publicly about what you built and how Zerops is used.
File the form here with your repository, live URL, demo, and post.
Your build post
Step three is a public post about what you built, and the link to it goes in the submission form. It has to carry:
AI-use policy
Read before you submitAI can help you build it. It can't build it for you.
Use it for code, debugging, tests, design, or docs. A project generated entirely by AI, with no meaningful work of your own, is rejected - however good it looks.
What you're held to
05 / Kickoff livestream
Saturday, August 8. Watch it live, or catch it here afterwards.
Saturday, August 8 · Livestream
An introduction to Zerops, a walk through the challenge and what a submission needs, and a live look at a working deployment. Bring your questions and ask them before you start building.
Watch on YouTube06 / About Zerops
The platform your project runs on, and the one file it takes to get there.
Zerops
A developer-first cloud platform for building, deploying, and running applications. Runtimes, containers, databases, brokers and storage in one project, wired together over a private network.
You keep control of the environment your application runs in, with a lot less infrastructure work between you and a product online.
zerops.yaml
in your repository
zerops: - setup: api build: base: nodejs@22 buildCommands: - bun install - bun run build deployFiles: ./ run: base: nodejs@22 ports: - port: 3000 httpSupport: true start: bun run startOne file describes how the application is built, deployed, and run. Push, and Zerops does the rest.
07 / What can you build
Any category, as long as the finished project is deployed on Zerops.
A research assistant, document platform, support agent, or knowledge search tool with a real backend behind it.
An uptime monitor, deployment dashboard, API workspace, feature flag service, or status page.
A collaborative editor, multiplayer workspace, live incident room, or shared planning tool.
Document conversion, image processing, report generation, data ingestion, webhooks, or scheduled jobs.
A booking platform, project management tool, creator product, or business operations dashboard.
A zerops.yaml generator, deployment analyser, migration assistant, or architecture visualiser.
08 / FAQ
Yes. The event is completely online, and you can take part from anywhere.
Right here. The registration block sits at the top of this page - sign in, register, and you're in.
On this page too. The submission form opens when the event starts, and you won't need to fill in a separate external form anywhere else.
Your project must be deployed on Zerops, and Zerops must be meaningfully involved in how the application is built, deployed, or operated.
Yes. You may use any programming language, framework, database, or open-source technology that works for your project and your deployment.
No. The challenge is solo only. You build on your own, and each participant submits a single project.
Yes, for development, debugging, testing, design, or documentation - and you must disclose it in the submission form. What you can't do is submit something you don't understand: you should be able to explain the architecture, the code, and the decisions behind them. Projects generated entirely by AI, with no meaningful contribution of your own, will be rejected.
Yes. A public source code repository is required for judging.
Yes. The deployed application must remain available until judging is complete.
The WeMakeDevs Discord, on the official event channels. Questions about Zerops itself are best answered by the Zerops documentation and community, both linked on this page.
Registration is open now, and it closes when the event does. Read the rules before you start building.