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
Sort by:
Autonomous GitLab Duo multi-agent engine that executes all 9 post-code DevSecOps stages (Plan to Govern) with Claude & Vertex AI while cutting pipeline carbon intensity (SCI) by 87.9%.
A system that tests proposed security changes against realistic AI workloads before production rollout.
GitLab Duo agents that guard money code for micro-lenders: they catch money bugs, write failing tests, fix pipelines, prove the ledger balances on Cloud Run, then ask you to approve the release.
Your incident response has a detonation problem. Ours doesn’t.
Ribhu finds the code an upstream API upgrade will break. GitLab Duo flows plan and repair the fix, and CI proves it on staging and production before release.
A fire drill for every merge request. We break the APIs and databases your code depends on, and it only ships if users hear about it and the app recovers.
Your codebase has your number. Production phones the on-call engineer, a GitLab Duo flow brings the fix, and one spoken word ships it.
Spider-Web: issues travel only the strands they need, from triage and test-first build to targeted review, auto-merge and Cloud Run deploy.
Don't trust the agent. PROVE it. GitLab Duo delivery where the agent that writes the code never approves it: separate gates, identities and a blind Oracle decide the merge.
Zero-touch autonomous DevSecOps: self-heals broken pipelines and security flaws from crash to deploy.
Your agents write the infrastructure. ProofGate proves it does exactly what you agreed, live, signed and nothing more, before it ever reaches production.
One sentence. A whole drop.
Ever used open source packages that the maintainers stopped maintaining? Upkeep adopts them: GitLab Duo agents fork, fix, publish and keep them updated with security patches and version upgrades.
GitLab Duo agents that catch, explain, and fix web accessibility barriers in every merge request. Fixed 8 of 8 planted barriers and 75 of 76 real ones in popular open-source templates.
When the National Weather Service warns your area, Stormproof load-tests your outage map at storm traffic, scales it up and freezes risky deploys, with GitLab Duo agents running the storm.
A red monitor does not prove an alert arrived. Proof of Alert checks saved DOWN and recovery receipts, then follows a GitLab Duo repair through canary and production checks.
Follow named connections in a real Excalidraw drawing, edit the scene and reopen your changes. Accessible Canvas checks the destination behind each arrow before releasing the editor.
An offline purchase, a transfer and a retried salary should still describe one household budget. Follow the real transactions through a repair that stops duplicate income.
Update the delivery backend while an older scanner keeps working. Follow each parcel from acknowledgement to one recorded delivery, including its photo reference.
Share a support ticket while keeping private notes private. Relay Desk checks who sees each field, then follows a GitLab Duo repair through real release checks.
a supply-chain attack gate inside your GitLab pipeline.
A CI drill and a GitLab Duo flow that prove a release can be rolled back before it ships, and open the fix merge request when it cannot.
Turn GitLab issues into tested changes and guarded releases, with risk-based human approval and an auditable deployment trail.
Every merge request earns its own level of autonomy from evidence, and loses it exactly where production proves it wrong.
