Chassis · Merkava Drive

Project management for ops and engineering.

One Drive for the whole team. Operations work and engineering work in the same kanban, with Forge AI scaffolding the parts you'd otherwise skip.

Chassis kanban with To-do, Doing, Blocked, and Done columns; tasks show owners, priorities, and linked GitHub PR numbers

One Drive, four ways to see your work.

Same project, same data. Pick the view that matches the question you're answering.

Kanban view — four columns, drag-and-drop, live updates across tabs
Timeline view with weekly bars
Timeline · weeks · gantt bars
Tree view with epic, story, and subtask hierarchy
Tree · epic → story → subtask
Weekly time-tracking strip with billable hours
Time · billable hours · /me strip
Forge — in the box

Forge AI does the parts you'd skip.

No prompt-writing. Forge is a surface, not a chatbox — it sits next to the work, ready when you need it.

Forge subtask-suggest popover proposing five concrete subtasks with checkboxes
Suggest subtasks

3–5 children, one click.

Forge proposes shippable pieces with descriptions and creates them as children of the parent task.

Sprint retro

Auto-written, grounded.

When a cycle closes, Forge writes what shipped, what slipped, keep / cut / start — from the activity log.

Weekly digest

Operator voice.

Shipped this week, heads up next week. A tight markdown brief you can paste anywhere.

Starter project

Scaffold from venture.

First open. Forge reads Crew, Atlas, and Centerline bearings; proposes a starter project with seeded tasks.

Built for the way you actually run a team.

Cadence, code, and people aren't separate tools when you're running a small team. Chassis treats them as one system.

Centerline scorecard rows linked to Chassis project breakdowns
Cadence

Centerline bearings become projects.

A quarterly bearing promotes straight into Chassis as a project with milestones and owners. No re-keying.

Code

GitHub sync, both directions.

Set github_repo on a project. Import, reconcile, export, auto-close — the surface flips on.

People

Owners are Crew records.

One canonical person across the cockpit. Crew, Atlas, and Gauge all read the same record.

Connect everything.

Public REST API, signed webhooks, automation rules, intake forms. Build whatever wiring your stack needs without a Zapier middleman.

Automation rules configured per project — when this happens, do that
Build

Public API + intake forms.

Bearer-auth REST at /api/v1/chassis/*. Each project can publish a public intake form at /forms/:slug.

Ship

Slack-native + signed webhooks.

Point a webhook at a Slack URL — Chassis emits real Block Kit. Generic URLs get HMAC-signed JSON.

Watch

Automation rules, server-side.

When status flips, when due_on passes, when a field changes — post to Slack, DM the owner, hit a webhook, set a field.

Built for the way you work.

Read the page that describes the work you do today.

Pricing.

Standalone, or bundled into a Merkava executive. The cockpit is free; you only pay for the Drives you use.

Standalone
$49/mo

Tier 2 Drive. Just Chassis, no exec hire. Right when you already have an OPS or TECH exec elsewhere.

Bundled — TECH
$149/mo

CTO + 3 specialists. Includes Chassis, Atlas, Beacon. Right path for engineering-heavy teams.

Bundled — OPS
$299/mo

COO + 8 specialists. Includes Chassis, Centerline, Crew, Gauge, and four more. Right path for ops-heavy teams.

Full C-Suite
$599/mo

Everything. All five execs, every Drive in the box.

7-day free trial on first install. Annual billing saves 20%.

Questions.

What is Chassis for?

Chassis is the project layer for operators running both operations and engineering. It carries projects with owners, due dates, milestones, and a four-column kanban. Use it for partnership rollouts, hiring drives, pricing changes, infra migrations, and engineering sprints in the same workspace. Centerline bearings promote into Chassis projects without re-keying.

How is the operations view different from the engineering view?

Same Drive, same data spine. The difference is one field on the project: github_repo. Leave it empty and you get the operations view. Set it and Chassis flips on the engineering surface — sync banner, GitHub issue + PR URL fields on every task, Create-GitHub-issue button per task, auto-close-on-done.

What does the GitHub sync actually do?

Four flows. Import pulls open issues and PRs from the linked repo and creates Chassis tasks for items not yet linked. Reconcile fetches GitHub state for already-linked tasks and flips them to done when an issue closes or a PR merges. Export creates a fresh GitHub issue from a Chassis task with no linked URL. Close auto-closes the linked GitHub issue when a task flips to done.

How does Chassis work with Centerline?

Centerline runs the cadence — weekly review, quarterly bearings, scorecard. Chassis runs the breakdown. A bearing is a quarterly objective; Chassis turns it into a project with tasks, milestones, and owners. The OPS executive ($299/mo) operates Centerline + Chassis + Crew + Gauge as one system.

Will Chassis replace Linear, Asana, or Jira?

For project management inside Merkava, yes. Where Chassis wins: native to the cockpit, Forge AI workflows ship in the box, GitHub bidirectional sync is included. Where the standalones still win: Linear's keyboard speed, Asana's integration breadth, Jira's enterprise reporting depth. See the vs-Linear, vs-Asana, and vs-Jira pages for honest broker comparisons.

What does Chassis cost?

Tier 2 · $49/mo as a standalone Drive subscription. Bundled into both the OPS executive ($299/mo) and the TECH executive ($149/mo) — same Drive, two ways to expense it. C-Suite ($599/mo) includes everything. 7-day free trial on first install. Annual billing saves 20%.

How do the Forge AI workflows work?

Forge is the AI engine inside Merkava. Inside Chassis: scaffolds a starter project from your venture profile; proposes 3–5 concrete subtasks with descriptions; writes the end-of-sprint retro automatically when a cycle closes; generates a weekly progress digest in operator voice; drives a one-click first-sprint wizard. None of these require a prompt.

Can I migrate from my existing tool?

Yes for engineering: link a GitHub repo, hit Import, and your open issues and PRs become Chassis tasks. For operations work moving in from Asana, Notion, or a spreadsheet, the lift is manual today. We will help if you ask: [email protected].

Run your projects in the cockpit.

Sign up for Merkava and install Chassis from the Garage. 7-day free trial on first install.