Life After Code

Overview

Life After Code is the GitLab Transcend Hackathon, focusing on extending automation in the DevSecOps lifecycle beyond initial code generation. Participants are tasked with creating agents and flows utilizing the GitLab Duo Agent Platform to automate various stages such as code review, security scanning, testing, compliance, deployment, and monitoring. The challenge encourages participants to determine the level of control they hand over to the automation, ranging from assisted to fully hands-off systems. Contestants must choose one of two paths: "Start Fresh," where they build a new AI-powered project on GitLab with CI/CD and automation from scratch, or "Bring Your Own," where they integrate AI-powered post-code automation around an existing MIT-licensed open-source project and deploy it. All projects must incorporate features from the GitLab Duo Agent Platform, such as agents, flows, or MCP clients. Deploying on Google Cloud offers eligibility for bonus points. There is a total of $45,000 in cash prizes distributed across various categories, including the best agents at each autonomy level for both paths, most DevSecOps stages covered, most environmentally impactful, and most creative projects. Judges from GitLab, Google, and Anthropic will evaluate submissions based on technological implementation, design, potential impact, innovation, and presentation. To participate, individuals must register on Devpost, complete GitLab Transcend Hackathon contributor onboarding, and build their agent using the Duo Agent Platform quickstart. Key dates include a submission deadline of October 27, 2026, at 1:00 PM UTC, with winners announced on or around November 16, 2026. The hackathon is open to individuals above the legal age of majority in their country of residence, with specific country exclusions.

What to build

Participants must build a project using GitLab Duo Agent Platform features (agents, flows, or MCP clients) that automates the post-code DevSecOps lifecycle. Projects must fit one of three levels of autonomy: Assisted (approve every step), Supervised (approve outcome, not individual steps), or Hands-off (set intent and walk away). Participants must choose one of two paths: * Path A: Start Fresh: Build a new AI-powered project on GitLab that demonstrates agentic automation of the post-code lifecycle. This includes creating the app, CI/CD pipeline, and automation from scratch. The project must be new work created specifically for this hackathon. Deployment is optional, but deploying on Google Cloud is eligible for bonus points. * Path B: Bring Your Own: Take an existing MIT-licensed open-source project (yours or a fork), import it to GitLab, build AI-powered post-code automation around it, and deploy it. The automation and deployment must be new work, done on or after October 5th. Deployment can be anywhere, but deploying on Google Cloud is eligible for bonus points. The core challenge is to build automation that reaches across as many of GitLab’s DevSecOps lifecycle stages as possible: plan, create, verify, package, secure, release, configure, monitor, govern. Touching a stage counts; using every feature within a stage is not required.

Prizes

Key dates

• Build Session with Missy Davies and Dennis MeisterOctober 9, 2026, 10:00 AM ET
• Submission DeadlineOctober 27, 2026, 1:00 PM UTC
• Winners AnnouncedOn or around November 16, 2026

Eligibility

Participants must be above the legal age of majority in their country of residence. Specific countries/territories are excluded: Brazil, China, Crimea, Cuba, Donetsk People’s Republic, Iran (Islamic Republic of), Korea (Democratic People’s Republic), Luhansk People’s Republic, Quebec, Russia, Syrian Arab Republic.

How to enter

1. Register for the hackathon on Devpost.
2. Start GitLab Transcend Hackathon contributor onboarding (approximately 5 minutes, plus about 24 hours for approval).
3. Build your first agent with the Duo Agent Platform quickstart (approximately 45 minutes).
4. Read the two Paths (Start Fresh or Bring Your Own) and pick one, then browse the DevSecOps lifecycle stages and plan how many your agents and flows can reach (approximately 30 minutes).
5. Build your project, using GitLab Duo Agent Platform features such as agents, flows, or MCP clients, adhering to the chosen path and autonomy level.
6. Submit your project on Devpost by the deadline.

Submission requirements

• Project must use GitLab Duo Agent Platform features (agents, flows, or MCP clients).
• A text description of what your project does, the problem it solves, and how GitLab was used to automate the post-code lifecycle.
• A public GitLab Project with all source code, assets, and instructions needed to run the project. It must include an MIT License file, visible at the top of the repository page in the About section.
• Visible CI/CD pipeline history showing your automation running.
• A demo video under three minutes, uploaded to YouTube and publicly visible, demonstrating the automation running (no third-party trademarks or copyrighted music).
• For **Path B: Bring Your Own** only: Explain what was added or changed during the Submission Period. The agentic automation and deployment must be new work, done on or after October 5th. Provide a URL to your deployed project (must stay live until winners are announced). Provide a URL to the original MIT-licensed open-source project you started from.
• Optional for Google Cloud bonus: Include your Google Cloud deployment code in your public GitLab repository and provide a link to your live project on Google Cloud (must be public and available to judges).

Judging criteria

• Technological Implementation: How thoroughly and skillfully the project uses GitLab to automate the post-code DevSecOps lifecycle; code and pipeline config reflect genuine effort and a working, non-trivial implementation.
• Design: Project delivers a complete, coherent end-to-end workflow, not just a technical proof of concept.
• Potential Impact: Project makes a credible, specific case for solving a real problem for a real audience, and the solution actually addresses that problem based on what's demonstrated.
• Innovation / Idea: How creative and novel the concept is and how inventively it applies agentic automation compared to existing concepts.
• Presentation: Video clearly demonstrates the automation running end-to-end; communicates what problem is solved, who it's for, and why it matters; overall presentation is easy to follow.

Sponsors & partners