Next liveBuild Your Own Calendly · zoomwithchipp.comSave your seat →

For agencies

An AI engineer in every app you build.

Every app you start on Chipp has autonomous development built in. Your clients ask for changes, your AI engineer builds them, and you stay in control of what ships.

The tickets list: one ticket needing approval over its budget cap, one running, and three succeeded with their cost
Real screenshot of the Chipp software factory, with example data.

Autonomous development, built into every app

You do not bolt on a separate dev team or a ticket tool. The AI Engineer is part of the project from the first day.

Take a request from a client, approve it, and watch it get built, tested and released.

Build

An AI Engineer on every project

Every project has its own AI Engineer. It builds and changes the app, and it files tickets for the work.

Your clients never have to learn a new tool to get a change made.

Ask

Clients ask where they already are

Connect the AI Engineer to Slack and work in a channel with your client. Or switch on the Support page inside the app, so signed-in users can report bugs and ask for changes.

Ship

You approve, it builds, it goes live

Every request waits for your approval. Approved work is built and tested, then released the way you choose: as soon as it is built, on a schedule, or when you press Deploy now.

From a client request to a live release

  1. 1ConnectCreate the project agent once, and connect it to Slack.
  2. 2Clients askIn a Slack thread, or from the Support page in the app.
  3. 3You approveReview the request, edit it, and approve it.
  4. 4It shipsThe AI Engineer builds it, and it goes live the way you set.

Slack

Build the app from a channel with your client

Connect your project's AI Engineer to Slack, invite it to a client channel, and @mention it. It reads the thread, asks a question if it needs one, and proposes the work as a ticket.

  • Create a Slack app from Chipp's manifest, paste its credentials, and install it.
  • The agent posts a card with Approve and Reject. Nothing runs until someone approves.
  • The result comes back to the same thread, and the ticket shows in your Tickets list.
The Slack setup dialog in the Chipp Software Factory: create a Slack app from a manifest, then add credentials and install

Support page

Turn on a Support page in your client's app

Switch on the built-in Support page, and signed-in users can ask your team for fixes and changes from inside the app, in a chat or a form.

  • Choose which kinds of request to allow: bug reports, feature requests and change requests.
  • Set limits per user and per app each day, and a budget for each ticket.
  • Show it inside your app's own layout, or as a separate page for your app's users.
The Support page settings for the Harbor Fitness app: a switch, where the page shows, the kinds of request allowed and daily limits

Approvals

Every request waits for you

Client requests land in "Needs your approval". Only your approval starts a ticket, with your credits and the project's budget caps.

  • Approve it, edit it first, or send it to the Builder.
  • Decline, mark it resolved, or mark it as a duplicate. Users are told when it was already reported.
  • Block a user who sends noise.
Three client support requests waiting for approval, each with Approve, Approve in Builder, Edit then approve, Decline, Mark resolved, Duplicate and Block user

Autonomous development

Watch approved work get built

Approved tickets run on their own in an isolated sandbox against your project's repository. You see what is running, what finished and what it cost.

  • A ticket over its budget cap waits for you to approve, re-plan within the cap, or reject.
  • Finished work merges into the project, and the release setting decides when it goes live.
  • Choose Continuous and each merge goes live as soon as its build finishes.
The tickets list: one ticket needing approval over its budget cap, one running, and three succeeded with their cost

Version control

Every release is a version, with one-step rollback

The Releases tab keeps the history of your app. See what shipped and when, and roll back to an earlier version if you need to.

  • Pick how work goes live: Continuous, Manual or Scheduled. New projects start on Manual.
  • Switch on the What's new page, so every release lists what changed for your clients.
  • Switch on the Update prompt, so people with the app open get an "Update now" card.
The Releases tab: a What's new page switch with five versions listed, and an Update prompt switch

What's new

A What's new page your clients can read

Each version gets plain-language release notes. Your client can search them and filter by New, Improved, Fixed and Removed, so they always know what changed.

  • It publishes at your app's own address, with no rebuild.
  • Only public release notes show.
  • Your app gets a "What's new" link, and the Update prompt links to the page.
The public What's new page a client sees: a search box, filters for New, Improved and Fixed, the current release and earlier releases

Screenshots are real captures of the Chipp software factory, with example data from a fictional app.

You stay in control of what ships

  • You approve every requestSupport requests and Slack proposals both wait for your approval before any work starts.
  • Budget capsSet a budget for each ticket. A ticket that needs more waits for your say.
  • You choose how it goes liveContinuous, Manual or Scheduled. New projects start on Manual.
  • Roll back in one stepPut an earlier version back live. A rollback restores code, not data.

Frequently asked questions

Is there really an AI engineer on every app?

Every project has one AI Engineer. It builds and changes the app and files tickets. People who use your app do not talk to it. To use it in Slack, you create the project agent once on the Connections page.

Does anything ship without my approval?

No. Every Support request and every Slack proposal waits for your approval before any work starts. You also choose how finished work goes live: Continuous, Manual or Scheduled.

How fast does a fix go live?

It depends on the ticket and on your release setting. With Continuous, finished work goes live as soon as its build finishes. New projects start on Manual, where someone presses Deploy now.

What does it cost?

Tickets draw on your credits, and you can set a budget for each ticket. The autonomous ticket system and the AI Engineer in Slack are part of a paid plan. See the pricing page for which plan includes them.

Can my client see what changed?

Yes. Switch on the What's new page, and every release lists what changed. Only public release notes show. You can also switch on an Update prompt for people who have the app open.

Can I undo a release?

Yes. The Releases tab lists earlier deploys, and you can roll back to one in a single step. A rollback restores code, not data.

Can I use this for clients in healthcare?

Yes, with the right plan, HIPAA mode and a signed BAA. See the security page for what each one covers.

Give every client app an AI engineer.