Open source · Self-hosted · Apache 2.0

Glide fromidea toshipped.

A new way to build software. AI agents scope the request, write the spec and forecast the date. Your team reviews and decides. No sprints, no story points, no standups.

Get started on GitHub
npx glideship init

A Glideship board. One feature, "Search across projects and comments", moves from BUD to production while each agent finishes its step.

WATCH A FEATURE GLIDEBUD-009 / Search across projects and commentsDemo board
  1. Triage Agent Scoped from Slack
  2. BUD Agent Spec written
  3. Design Agent Wireframes ready
  4. Tech Plan Agent Plan ready
  5. Smart Assignment Assigned to Lucas: best skills, free this week
  6. Status Agent Approved and merged to main
  7. Test Plan Agent 14 tests passing
  8. Bug Linker Agent Clear to release
  9. Status Agent Live in production
  10. Learning Agent Retrospective saved
What changes

Less process.
More shipped.

Scrum & Jira vs Glideship

Every Scrum ceremony, replaced.

Standups
A daily status meeting
The Standup Agent writes the daily update for you
Sprint planning
Two-week sprints and capacity maths
Work flows all the time, with forecast dates
Backlog grooming
Weekly grooming meetings
The Triage Agent scopes work as it arrives
Retrospectives
A retro after the damage is done
The Learning Agent writes one every time a BUD closes
See the full comparison
Replace the wiki

Code is the truth.

Glideship learns from your code, not your wiki. Every time a pull request merges into your main branch, it re-learns what changed and shares it with every agent. So specs, plans and tests match what the code really does, not what someone remembers.

See how knowledge syncs
Features: the live feature list Glideship builds by scanning your code
Gamification, done honestly

XP for shipping. Not for activity.

Whatever you measure, people learn to game. So Glideship rewards just one thing: work that reaches production. The game and the goal are the same.

  • Outcomes, not activity
    XP lands when work is merged, reaches UAT and goes live in production. Never for ticket counts, hours logged or lines of code.
  • Shared on shipping
    When a BUD ships, the XP is shared by everyone who contributed commits or pull requests. Helping a teammate never costs you.
  • Recognition, not surveillance
    Leaderboards celebrate what shipped. Streaks and mini-games keep things fun, but they never count toward work XP.
  • Levels unlock rewards
    Good outcomes earn skill points to spend on unlocks and badges. Fun stays fun, and reviews stay reviews.
Leaderboard ranked by shipped value — what reached production, not ticket count
No lock-in, either direction

Bring your backlog.
Bring your AI.

Jira import — connect Jira Cloud and import issues into BUDs

Bring your Jira. Then leave it behind.

Connect Jira Cloud and turn your existing issues into BUDs in minutes. From there, the agents run the process.

MCP support — connect your local AI assistant to Glideship

Bring your own AI.

Run the agents on Claude Code, GitHub Copilot, OpenAI Codex or a local Ollama model. With Ollama, nothing leaves your network. Your coding assistant also connects through MCP, the open standard for plugging AI tools into apps, to read your team's context and draft BUDs. Every change is saved, so you can undo it in one click.

Ship the work. Skip the ceremony.

Get started on GitHub

One command. Needs Docker and Node.js 18 or later. Your code and data stay on your machine. npx glideship init