Cookies, only with your consent

We use cookies to understand how the site is used and to improve our advertising. Essential cookies are always on. We turn on the rest only if you agree.Essential cookies are always on. Measurement and marketing only if you agree. Privacy policy

What may we measure?

You can change your choice at any time from "Cookie settings" at the bottom of the page.

Choose language: English
Log inJoin the waitlistJoin waitlist
Build with your troupe

Build what your business needs. Your troupe already knows how to run it.

Ask in chat for a site, a form, an internal tool, or a whole app. Your troupe writes the code in a private cloud workspace, shows it to you running, and sends it to GitHub only after you approve. And in the same conversation, it connects it to your automations.

Signups are closed for now · opening gradually

What you need: your code on GitHub, or nothing: your troupe starts a new app from scratch. JavaScript, TypeScript, Python and more.

  • You're in controlEvery change in plain words and as the exact code, arriving as a pull request. Never straight to the main branch.
  • The key stays with youGitHub access never enters the workspace the code runs in.
  • You see everythingA live preview link, and a live log of every command.
  • From your phoneA notification when something is ready, and approval with a tap.
  • Only what runsWhen there's no task, the workspace switches itself off. No charges build up for time when nobody was working.
  • Already connectedWhat you build works with your troupe from the first minute.
What you build with your troupe

From a small tool for your business to a whole app.

Ask in your business's own words. Each tile is a real request, and what you get back.

  • Business owners

    Internal tool: a booking system

    Ask: A booking calendar for three barbers, with a WhatsApp reminder the day before.

    A new app in your GitHub, and the Drummer is already sending the reminders.

    • New app from scratch
    • Connected to an automation
  • Marketing

    Campaign landing page

    Ask: A page for the holiday sale, with a form, and every lead goes to the Lead Singer.

    A new page on your existing site, as a pull request. Every lead goes straight into the campaign automation.

    • On your existing code
    • Connected to an automation
  • Agencies and service businesses

    Client portal

    Ask: A personal area where each client sees their order status and invoices.

    A portal with login, updated from the systems already connected to your troupe.

    • New app from scratch
    • Python or TypeScript
  • Sites on Wix, WordPress and Shopify

    A form that talks to your troupe

    Ask: Have the form on our Wix site send leads straight to you.

    A short snippet to paste. No server, no key in the browser, and it only accepts submissions from your site.

    • No GitHub
    • No server
  • Developers

    Nightly maintenance

    Ask: Every night, update dependencies, run the tests, and open a pull request if everything passes.

    A pull request ready in the morning, and an approval notification on your phone.

    • Runs on a schedule
    • Approve from a notification
  • Developers and anyone maintaining a product

    From issue to fix

    Ask: For every issue labelled "bug": fix it, add a test, and open a pull request.

    A fix with a test that proves it. And if CI is red, your troupe reads the error and fixes it again.

    • Runs on an event
    • Fixes red CI
How it works

Four steps, and you decide at each one.

From the request to your troupe running what it built. All in the same conversation, in your language.

  1. 1 · Ask

    Say what you need

    On an existing project, or a new app from scratch. Your troupe remembers the project between conversations, so you don't explain everything again.

  2. 2 · Your troupe builds and tests

    See every command

    In a private cloud workspace for each project: it installs, writes and runs tests. JavaScript, TypeScript, Python and more.

  3. 3 · Dress rehearsal and approval

    See it running, then approve

    A live preview link, a plain-language summary and the exact change. Approve, and a pull request opens. Merging stays with you.

  4. 4 · Your troupe runs it

    And it already works

    In the same conversation, your troupe connects what it built to your automations, and the connection secret is written straight into your hosting settings. After the merge, it works.

You're in control

Nothing enters your code without your approval.

Every change comes with an explanation you can read, and with the exact change for anyone who wants to check it line by line.

  • Plain-language summaryAbove every change: what will change in your business, in your words. You don't need to read code to decide.
  • The exact changeEvery file and every line, before anything is sent to GitHub.
  • Pull requests only. Never the main branch.No force-push, no overwriting other people's work. Merging stays with you.
  • The key stays with youGitHub access never enters the workspace the code runs in. Connection secrets go straight into settings, without your troupe seeing them.
  • A log of every actionWho asked, who approved, which command ran and when. All of it is kept.
From your phone

The client asked for a change. You approved it on the go.

Your troupe works on the code even when you're away from your computer. You get a notification, see what will change, and approve from anywhere.

  1. A notification when something's readyA real notification on your phone, even when Troupia is closed.
  2. See what will change, in wordsThe plain summary on top, and the exact change a tap away.
  3. Approve with a tapOn iPhone and Android, with nothing to install from an app store.
Runs on its own

Coding jobs that start without you asking.

Like any troupe automation: on a schedule or from an event. The difference is that here your troupe works on the code. And even while you sleep, nothing goes out without your approval.

  • On a scheduleEvery night: dependency updates and tests. In the morning, a pull request is waiting.
  • From a labelled issueA "bug" on GitHub becomes a fix and a pull request.
  • When CI is redYour troupe reads the error, fixes it, and sends it back for approval.
  • From a business eventA new sale on the calendar? The landing page is updated, and waits for approval.
Who it's for

For anyone the business needs something new from.

  • Business owners

    You have an idea for a tool, a form or a page, and no developer. Now you've got a troupe.

    • No code to write
    • See it running before you decide
    • What you build already works with your troupe
  • Agencies and freelancers

    Dozens of small requests from clients, from anywhere, at any hour. The client asks, and you approve on the go.

    • A separate project and workspace for each client
    • Invite a client to a project, with limited permissions
    • Build a client a form, and connect it to their troupe
    Work this way on your clients' sites
  • Developers

    A band member who does the repetitive work, and hands it in the way you're used to.

    • Reviewable pull requests, with tests
    • Long commands, a full log, and an interactive terminal
    • GitHub, GitLab and Bitbucket
What it costs

You pay only for what runs.

  • It's part of the plan you already have. Your troupe's work on code uses the same credits.
  • When there's no task, the workspace switches itself off, so no charges build up for time when nobody was working.
  • Before a big job you see an estimate, and afterwards a report of what ran.
  • A spending cap you set. No surprises on the bill.
See all plans

A normal day on the "Workshops" project (illustration)

Building and testingRunning

Live previewRunning

Waiting for your approvalOff

OvernightOff

Questions

What's worth knowing before you start.

What do I need to get started?
A troupe on Troupia, and a GitHub account. No code yet? Your troupe opens a new project for you. Site on Wix, WordPress or Shopify? You don't even need that: you get a short snippet to paste.
Which languages?
JavaScript and TypeScript, Python and more, with npm, yarn, pnpm or bun. The conversation itself runs in English, or in any of Troupia's eight languages.
Can I do it without GitHub?
Yes. GitLab and Bitbucket work too. And a Wix, WordPress or Shopify site needs no code repository at all: paste the form snippet, and leads reach your troupe.
Who sees my code?
Only you and your troupe.
What happens if something breaks?
Nothing goes in without approval, so your main branch is safe. If a test fails, your troupe reads the error, fixes it and sends it back for approval. Already merged and something's wrong? Say "undo that", and a pull request that reverts it opens.
How much does it cost?
It's part of your plan, and you pay only for what runs. When there's no task, the workspace switches itself off, so no charges build up for time when nobody was working. Before a big job you see an estimate. See all plans
  • the Robot
  • the Drummer
  • the Lead Singer

Something your business needs? Let your troupe build it.

You ask and approve. Your troupe builds, tests, and runs it.

Join the waitlistSignups are closed for now. People on the list get access first.Works with GitHub. GitHub is a trademark of GitHub, Inc.

Accessibility

Signups aren't open yet

Be the first, right in the front row

We're in final rehearsals. Leave your details, and we'll send you a personal invitation the moment the curtain rises.Leave your email, and we'll send a personal invitation when the curtain rises.

No spam, ever. Privacy policy