The app builder IT will actually approve.

For enterprise teams and individual builders who want real apps: built on your own computer, with the AI you already pay for, and saved to your company’s git, where IT can review every app and decide what ships.

Free for macOS, Windows and Linux.

For IT and teams

Works with Claude Code, OpenAI Codex and opencode, or your company’s AI through Bedrock, Vertex AI or Foundry. Free for macOS, Windows and Linux.

Five problems with building apps on AI today

And what Jig does about each one, with what ships today.

  • For individual builders

    AI builders charge you again for AI you already pay for.

    Jig drives the assistant on your own plan: your Claude subscription through Claude Code, your ChatGPT plan through OpenAI Codex, or other models through opencode. Companies can use their own AI through Bedrock, Vertex AI or Foundry. That provider bills you. Jig never charges for AI.

    Using the AI you already pay for
  • For individual builders

    Your apps live on someone else’s servers.

    Every project is a plain folder and git repository on your computer, with its history, plans, previews and keys beside it. Open it in any editor, publish to hosting you own, and there is nothing to export if you ever leave.

    What stays on your computer
  • For teams

    Everyone builds alone: the same tool five times, in five looks, with five security stories.

    Projects push to your company’s git, so teammates open the same app, carry on and review every checkpoint. Every project starts from the same templates and vetted skills. Company templates and a shared library are coming.

    How teams build together
  • For IT

    IT can’t see or approve what’s being built.

    Apps land in your git: GitHub, GitLab, Bitbucket or Azure DevOps, self-hosted too. A managed policy can make your servers the only place code goes, always private. IT sees what exists, reviews it, and picks what goes to production.

    What IT sees and controls
  • For everyone

    Keys and data leak into chats and tools.

    Keys live in your operating system’s keychain and the AI only sees their names. Pasted keys are caught, .env files are never shown or committed, and Jig’s servers never receive your code, prompts or keys.

    How keys and data are handled

Who Jig is for

For individuals

One place for every app you build

  • Every project as a folder and git repo, with its history, plans, previews and keys together
  • Your Claude or ChatGPT subscription does the work. No second AI bill
  • Checkpoints on every change, so you never lose a project
  • Publish where you want: Netlify, a zip, or a Dockerfile
Jig for individual builders

For companies

Control and visibility, without the ban

  • Every app lands in your company’s git, where IT can review it and choose what ships
  • A managed policy for allowed assistants, connections, git hosts and publish targets
  • Your company’s AI through Bedrock, Vertex AI or Foundry, an audit log, proxies and update control
  • Coming: company templates, a shared library, an admin dashboard, SSO and audit export
What IT gets with Jig

A real build, not a mockup

Jig with Dispatch Desk, the HVAC dispatch board it built, running in the preview beside the chatThe same app on a technician’s phone: today’s stops with Call, Directions and Finish job
An HVAC company’s dispatch board for the office, and the same app on a technician’s phone. The logo, portraits and illustrations were generated as it built.

Free forever for the local builder.

Jig never charges for AI. Your AI provider bills your usage directly, on the plan you already have.

Free
The full local builder, every connection and publishing.
Pro
Plus cloud backup to your own drive and priority support.
Enterprise
Plus your organization, managed updates and company controls.

Compare plans and pricing

Your next app starts in a folder you own.

Free to download. Bring the AI you already have.

Free for macOS, Windows and Linux.