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

Published in Software factory

Getting Started

The software factory generates and operates production software for you. You describe what you want, a team of AI agents does the engineering work (planning, implementation, testing, review, semantic merge, deployment, and verification), and the platform hosts the result at a live URL. There is no IDE to install and no CI to configure — the agents run in a sandbox, commit to your project’s real GitHub repo, and the platform rebuilds and rolls out the running app on every successful merge.

The AI does the building. It does not have to be part of what you run in production. A ticket can just as easily produce a backend API, a service-to-service integration, a scheduled job, an event processor, or a data pipeline as it can a web app, and none of those need to include a chatbot, an LLM call, or any other AI component in their runtime. Publishing a Chipp chat agent is one thing the software factory can build; it is not a requirement. See Software Factory Architecture: The Two Planes for how the development side (agents, tickets, review) and the production side (whatever you actually deploy) stay separate.

The lifecycle

  1. Create a project. Each project is backed by a GitHub repo cloned from the platform template. The repo is private and owned by the platform org; you can eject it to your own org at any time.
  2. Open a ticket. Tickets are how you ask for work — “add a login page”, “fix the bug where checkout 500s”, “switch the homepage hero to a video”. The platform routes each ticket to an agent.
  3. The agent runs. Inside an isolated build sandbox, the agent plans, implements, reviews, security-checks, and documents its diff. You can follow along in the Tickets view, or close the tab and come back later — every step is durable.
  4. The platform deploys. When the agent’s branch merges, a fresh build kicks off automatically. The new image rolls out behind the same Live URL, with a few seconds of crossover.

One product, not “website or app”

A project is one product. You never choose between a website and an app. Say what you want people to do, and the Builder adds what that needs: public pages, a form that saves submissions, sign-in, saved data, payments, or a signed-in dashboard.

The preview shows the part of the project you have open, for example the Landing site. The Builder works on that part first. If you ask the Landing site for a contact form that saves submissions, it builds the form and the storage behind it, and stays on the page. It adds signed-in screens only when you ask for a private dashboard, an account area or a workspace. If your request is unclear, the Builder asks one plain question about what you want people to do.

Name a website as the look

When you describe a new project, you can point at a website for its look, for example “use chipp.ai for the branding and look.” The Builder reads that site’s colors, fonts and corner style, and starts your project in that look. It skips the “Pick a look” step. You can review it on the planning screen and choose Change look to pick another one before planning starts. After that, change the look in chat or in the brand panel.

If the Builder cannot read the site, or finds no clear brand colors on it, it tells you which site it could not use and then shows the “Pick a look” step. A website you mention for another reason, such as a service the project connects to, is not used for the look.

Where things live

  • Tickets — every ticket and agent run, in progress and historical.
  • Project switcher (top of the sidebar) — pick a project. Its Overview, Deployment, and Settings tabs hold the repo, live URL, and per-project settings.
  • Back to project (top right of a full-page Builder session) — leaves the session and returns to the project’s page. The draft stays open: the sidebar’s Builder row takes you back to it. Back to classic, next to it, switches to the classic dashboard instead.
  • Domains — custom domains attached to a project.
  • Billing — credit balance, monthly usage, auto-topup, ticket charges, and funding receipts.
  • API Keys (software factory sidebar, under Platform) — create, copy once, and revoke your alch_ API keys. Owners and admins only.

Next steps

Ready to build it?

Tell Chipp what you want. Start free, or book a session and build it with our team.