# Models come and go. flower remembers.

flower gives your coding agents one shared memory, a place to plan the work, and a careful path from an idea to a deploy.

[Join the waitlist](/waitlist) · [How it works](/how-it-works)

## The meadow

Every build flower runs grows here as one flower, from first commit to deployed. [The meadow](/meadow)

## What flower does

### 01 Memory: Nothing is lost between sessions.

Every session is ingested as a full transcript and stays searchable, so the next agent picks up where the last one stopped.

### 02 Plan: Plan work, not prompts.

Work starts as a brief: what to build, how you will know it is done, and the context behind it.

### 03 Ship: Nothing ships unreviewed.

Every build is reviewed by a model from a different lab and checked before it lands and deploys.

[How a change goes from a session to a deploy](/how-it-works)

## Principles

1. [Nothing is lost between sessions.](/principles#nothing-is-lost)
2. [Every change can be traced.](/principles#traced)
3. [Contained by default.](/principles#contained)
4. [A second opinion on every change.](/principles#second-opinion)
5. [Checks decide, not the agent.](/principles#checks)
6. [You hold the keys.](/principles#keys)
7. [Honest numbers.](/principles#honest-numbers)
8. [Quiet by default.](/principles#quiet)

## What's growing

### [A dashboard across your projects](/growing#a-dashboard-across-your-projects)

12 November 2026: The app opens on a dashboard that reads across all your projects and shows what is happening now, what is running and what is ready to ship.

### [Ship and deploy from the app](/growing#ship-and-deploy-from-the-app)

12 November 2026: A project's page in the app has Ship and Deploy buttons, and the app can ask for your passkey before either one runs.

### [Mark yourself away](/growing#mark-yourself-away)

11 November 2026: Tell flower you're away until a set time, and it stops asking you to confirm things in your session until you're back.

[Every entry](/growing) · [Atom feed](/growing.xml)

## flower is built on a set of tools called polystrate.

Coding agents call these tools to remember their sessions, write and queue briefs, build, review, check and deploy changes, and ask a person for a decision. flower is one way to arrange them; polystrate is for people who want to arrange their own.

[What is in polystrate](/#polystrate)

## Early access is by invite.

Leave your email on the waitlist and we'll write when there's room for you.

[Join the waitlist](/waitlist) · [Already invited? Sign in](https://app.useflower.dev/)

It signs off with the tagline: Project memory and a build pipeline for builders of things.

The page prints the tagline as "Project memory and a build pipeline for coding agents", with "coding agents" struck through and "builders of things" written over it in pen. The correction opens a quote:

> You can just do things.
>
> — [Aaron Francis](https://x.com/aarondfrancis/status/1898056390649745459)

## What is in polystrate.

polystrate is the set of tools flower is built on: provenance, memory, briefs, builds, review and checks, deploys and messages. Permissions, secrets, decisions, standards and alerts apply to all of it.

[Read about polystrate and its early access at polystrate.dev](https://polystrate.dev)