Brace for impact.

We want to see your idea in production, fast. So three senior engineers get on it, each an expert in their field, with our own AI forge. Web, mobile, embedded, API: we build for every platform. All at a fixed price.

Pitch my idea

The plan first.

From your idea, we carve out with you the version that proves the most with the least: for which users, solving what, on what budget and timeline. The rest waits for v2. You leave with the first block's scope and its fixed price.

  • an idea
  • who for?
  • what need?
  • what constraints?
  • the plan

How we build

  1. The architecture is decided with you.

    This system has nine components, from the orchestrator to the robots. We put them on paper with you, push back on the brief where it needs it, and you leave with a quote per block: scope, deliverables, price, timeline.

  2. Your first users before the project is over.

    Here, the first block: the orchestrator and the pickers' app, enough to run the first robots. The price is fixed when you sign the quote; if the scope moves, a priced amendment before we go on.

  3. One ticket, one agent, one branch.

    Each block is split into tickets; in Singularity, our forge, an agent works each ticket in its own branch, tests and CI green before review, and we decide every merge. You follow along on a staging URL, in regular demos, with no project manager between you and us.

  4. Live in prod, monitored from day one.

    Space grade means CI/CD, infrastructure as code, zero-downtime deploys, rollback, and monitoring from the first release, here the orchestrator's queue, the gateway's latency, the control room's alerts. Then your team takes over, documentation included, or we run it.

We're founders too.

The three of us started Meteor Factory and we publish our own software, so we know what shipping a product takes. We build yours together: Antony on back end and infrastructure, Mehdi on front end and design, Marine on AI.

  • Antony Canut

    Full-stack developer, back end first. Architecture, SRE and DevOps.

    Worked for

    LinkedIn

  • Mehdi Chaabi

    Full-stack developer, front end first. Architecture, UX and UI design.

    Worked for

    LinkedIn

  • Marine Haziza

    AI and ML research engineer. Models and agents.

    Worked for

    LinkedIn

What we do

Build · fixed price

Start with one block.

We estimate the whole to give you the envelope, then you commit one block at a time: scope, deliverables, timeline, a price fixed when you sign. If the scope moves, a priced amendment before we go on.

POC
Validate a technical bet or get ready for a raise.
MVP / v1
A v1 you can sell, in production: auth, payments, deployment, monitoring.
Scale
New features, a redesign, more load.

Source code, repository, infrastructure and documentation are in your name from the first block, and you can stop after any of them.

Every block is covered for a month after it reaches production. Then your team takes over, or we run it for a monthly fee, no commitment.

Startups, scale-ups, SMEs and IT departments: an HR system, a CRM, a business application, a 3D landing page.

Software

What we publish.

Our own software, held to the standard your blocks are.

Singularity
The agentic development environment we build your blocks in: your requests become tickets, each handed to an agent in its own branch. Free on macOS, in beta.
Avocachet
The digital stamp for lawyers: exhibits numbered automatically, PDFs compressed, e-Barreau compliant.
Flare
Your Mac's notch made useful: music, shortcuts, notifications.

What we get asked before signing.

  • Fixed price or time and materials?

    Fixed price, always: a quote per block, the price fixed when you sign. On time and materials a vendor earns by lasting; on a fixed price, by delivering. If the scope moves, a priced amendment before we go on.

  • Who answers for the code the agents write?

    We do. Agents work tickets in Singularity, our forge; tests and CI pass before review, and one of the three of us decides every merge. What reaches production went through a senior engineer, who answers for it.

  • What if the scope moves mid-block?

    A priced, signed amendment before we go on, never a surprise on the invoice. The block keeps its price; what is added gets one too.

  • Who is my point of contact?

    One of the three of us, from the brief to production, and often all three. You talk to the people who design and ship.

  • Which technologies?

    The ones the project calls for. We choose the stack at scoping, with you, by your constraints and what your team can take over. Web, mobile, APIs, AI, infrastructure: we cover the chain.

  • Remote or on site?

    Remote, from France, with regular demos and a staging URL to follow along. On site when scoping or a milestone calls for it.

  • And after delivery?

    A month of bug fixes on what was delivered. Then your team takes over, with the code, repository, infrastructure and documentation in its name; or we run it, for a monthly fee, no commitment.

  • Where does our code go while the agents work?

    Where you decide. By default the repository stays on our machines and only the calls to the models leave, with our keys; if your constraints require it, models on premises or with the host of your choice. We lay out the options at scoping.

Your idea, in three lines.

Who it is for, what need, what constraints: what you already know is enough. One of the three of us replies within 48 business hours with a first read. If it is not for us, we say so, and point you elsewhere when we can.

Pitch my ideacontact@meteorfactory.dev