Fontan

Your users vote on ideas. A coding agent builds the ones you approve.

They test the beta inside your app, and nothing ships until you merge it.

Already running end to end on GitLab with Sip, a small Android water tracker.

Ideas board in Sip: a list of user posts with like counts and statuses such as Gathering likes, In review and Beta ready.

One tap installs the beta.

Five likes put it on your list.

The ideas board as users see it inside the app.

See how it works

One idea, from a post in your app to a release for everyone.

  1. 1 Users post

    Someone writes an idea or a problem, and others like it.

    Gathering likes
  2. 2 You decide

    Five likes put it on your list. You pick what gets built.

    In review
    Ideas board in Sip: posts grouped under In review and Gathering likes, with like counts.
  3. Not this one

    You say no with a reason, and the user sees it on their post.

    Declined
  4. 3 Agent codes

    It writes the change and its tests, then opens a merge request.

    Being built
  5. 4 Checks run

    A safety gate and the unit tests run before you look.

    Being built
  6. 5 Users test

    One tap installs the beta. One tap goes back to normal.

    Beta ready
    A post in beta with a Try this version button and the stage timeline below it.
  7. 6 Users confirm

    Testers say whether it works. You can send a problem back to the agent.

    Testers approved
  8. 7 You merge

    Everyone gets the update, and the post shows it shipped.

    Shipped
    Ideas board in Sip with the Night mode post under Shipped.

You act at three points. The agent and the checks do the rest.

You decide. The agent does the work.

Votes only put ideas on your list. The agent waits for you.

  1. Approve

    Nothing is built until you hand the idea to the agent.

  2. Send back

    If a tester finds a problem, you send it back for another try.

  3. Merge

    The agent cannot merge. Only you release.

Nothing risky gets through

Fixed checks, not the agent's judgement, decide what reaches you.

Safety gate

  • Only UI code changed
  • No test deleted
  • Under 400 lines
  • Unit tests passed
A gate on every change
The merge request fails if it touches code outside the UI, deletes a test or changes more than 400 lines.
No merge rights
The agent can open merge requests. It cannot merge or push to your main branch.
Starts only on your approval
Votes alone never start the agent.
Your app holds no keys
The repository token stays on the server, limited to one project.
Rollback any time
Testers go back to the stable version in one tap and keep their data.
Rate limits
Each device can send 5 posts and 30 comments a day.

Who it is for

Free during early access

We are onboarding a small group of developers now. Leave your email and we will write when your spot opens.

Only emails about Fontan access. No newsletter.

Questions

Can the agent ship something on its own?

No. It can only open a merge request, and only you can merge it.

What if a user writes a post to trick the agent?

The checks look at the code change itself, not at the post. A change outside the allowed area fails before you see it.

Does it work with Google Play? Planned

In Play apps the beta button will open your Play testing track instead of installing anything itself.

Which agent and tracker does it use? GitHub planned

GitLab with GitLab Duo works today. GitHub and a coding agent with your own key come next.

How long does one idea take?

In our first run, the agent built the change in about 8 minutes, and checks took about 10 more.