boucle.dev

Great ideas deserve to ship.

Landing page for boucle — a zero-code autonomous product builder. From a ticket in your forge to a feature in production, without running agents on your own machine.

Why boucle

Harness made for human, made by an indie product builder for product builders.

1. Lives in your forge — boucle lives in your forge (GitHub/GitLab). No external tool, no separate dashboard. Everything happens where you already work.
2. Deterministic and reliable — deterministic, therefore reliable. You intervene at the right moment, at the decision points.
3. Works while you sleep — the agent works overnight for you. You intervene only when it matters.
4. No UI, No CLI — no interface to learn, no command line to master. You interact through your forge: issues, comments, labels.
5. Self-healing, self-learning loop — a loop that learns from its mistakes, self-updates, and adapts to your codebase as your project advances.

How it works

boucle lives in your forge. GitHub, GitLab. No external tool, no dashboard.

1. Drop your idea in an issue — I create an issue in my forge with a title and a description. It's just a normal ticket.
2. Receive a proposal with a preview — boucle analyzes, writes a spec, and posts a comment on the issue with a preview. I see exactly what it will look like.
3. Approve or amend — I react with a thumbs up to approve the spec, or reply to amend it. No form, no CLI. Just an emoji or a comment.
4. It works — boucle implements, builds, deploys a preview. I have nothing to do meanwhile. The agent works.
5. It's verified — the reviewer checks the render, posts a verdict (PASS/FAIL) as a PR comment. If FAIL, it loops. If PASS, the PR is ready.
6. Approve, it's live — I approve the PR (or boucle merges per config). The feature ships to production. It's live.
7. Lessons learned — boucle captures what worked and what didn't from each loop, and applies those lessons to do better on the next feature.

Quick start

One command, and the loop takes over.

curl -fsSL https://boucle.dev/install.sh | bash

Then create an issue in your forge and tag it boucle:triage — the loop starts.

Brand

The boucle logo is a figurative afrofuturist face: a golden afro (the full circle = the "boucle"), gold hoop créoles, and an afrofuturist gold visor with the infinity loop (∞) woven into the bridge. The hero shows it as an animated GIF (public/boucle-logo.gif, 540×540) in a standalone column on desktop, with no decorative glow halo. public/boucle-logo.png serves the favicon and Open Graph image. A matching public/favicon.svg provides the 32×32 favicon.

Made in Africa by ankaboot.io.

Development

This is an Astro static site. Build and preview locally:

npm install
npm run build
npm run preview

The site is deployed to GitHub Pages at the custom domain https://boucle.dev/.

Editing content with Sveltia CMS

Every text and icon on the landing page is editable through the visual Sveltia CMS admin panel, without touching code or opening a PR manually. It is a client-side, Git-based editor served from the official CDN, running only at /admin/ (never on the public page).

1. Open https://boucle.dev/admin/.
2. Sign in with a GitHub Personal Access Token that has Contents: Read and write access to this repository (the "Sign in with Token" button links to the token page with the required scopes pre-selected).
3. Pick a collection (Hero, Steps, Cards, Quick start, Footer…) and edit any text field — or, for Steps and Cards, pick an icon from the Assets library (the Icon field is an image picker, not a text input). The Assets view lists every committed asset under public/ (including the 16 SVG icons in public/icons/ and the footer logo), so an editor can replace an icon's artwork directly from the CMS.
4. Save — commits the change to main with a [skip ci] suffix, so it does not redeploy. To make the change go live, open the Save dropdown and choose Save & Publish, which commits without the suffix and triggers the GitHub Pages rebuild. (The Save / Save & Publish dropdown is provided by Sveltia CMS via the skip_ci backend option in public/admin/config.yml.)

SVELTIA_PAT: the SVELTIA_PAT environment variable is reserved for the token so it can be injected via CI/CD. When the token is missing or invalid, the admin panel shows a clear sign-in error (it never renders a blank screen).

The CMS config lives in public/admin/config.yml and mirrors the Astro content collections (src/content/, schema in src/content.config.ts) 1:1, so an edit never loses data. The Sveltia CMS bundle does not load on the public landing page — zero performance impact.

License

AGPL-3.0