Flary

Open source. Installed in your account.

AI and email,
in your hands.

Choose a personal AI assistant, a team inbox, or agents for your app. Flary guides you through setup and deploys the result to your own Cloudflare account.

Choose your app

Apache-2.0 · Your infrastructure · Your provider accounts

One guided install. You sign in and choose what to use. Cloudflare and model-provider usage are billed to your accounts.

Choose your starting point

An assistant, an inbox,
or your next product.

01

Your AI assistant

Open a personal dashboard, choose a model provider, and connect the tools you use. Your assistant keeps its conversations and files between visits.

Install an assistant
02

Your team inbox

Receive and send email on your own domain. Give your team a familiar web inbox with replies, drafts, attachments, and live updates.

Explore Flary Mail
03

Agents in your app

Add an assistant to your existing product. Define its actions in TypeScript, then use the clients, React console, or embedded chat widget.

Build an agent backend

These are separate app templates. Choose one during setup, then customize the generated project. The guided CLI offers all three; the local browser installer currently focuses on an AI assistant.

One guided install

Make your choices.
Flary handles the setup.

01

Choose

Pick an app

Run the guided CLI to choose a dashboard, agent backend, or Mail. Already cloned the repo? Run npm run setup to open the assistant installer in your browser.

npx flary create
02

Connect

Use your accounts

Sign in to Cloudflare. Choose a model provider for AI, or a domain and mailboxes for email. Add browser and Sandbox resources when needed.

Browser sign-in
03

Launch

Open your app

Flary builds the project, provisions its resources, uploads secrets, deploys, and checks the result. Open the printed URL to finish owner setup or connect your existing app.

Your Cloudflare deployment
Serverless foundationWorkers · Durable Objects · D1 · R2 · Queues
Added by featureBrowser Run · Sandbox · Email Routing and Sending

The default AI setup needs no Docker or VPS. Sandbox command execution has additional requirements. Mail needs a domain; setup asks before changing its mail-routing records.See the deployment guide.

More than a model call

An assistant that can
keep working with you.

01

Pick your provider

Use your own model account or Workers AI. Connect services through MCP or OpenAPI and give each agent the tools it needs.

02

Keep the conversation

Return to the same thread, follow live activity, and resume accepted work after a disconnect or Worker restart.

03

Let agents work with files

Give an agent a persistent workspace to read, write, and edit. Keep Git history and checkpoints as the work progresses.

04

Stay involved

Ask for approval before an action, collect missing information, or request a secret through a protected form. The thread continues when you respond.

05

Add capabilities as needed

Enable browser automation, command execution, or specialized subagents when your application needs them. Optional services have their own setup and costs.

06

Make it your own

Edit the generated TypeScript, keep prompts in code or Markdown, and build your own interface. Your deployment stays in your Cloudflare account.

The framework also includes schedules, evaluations, usage tracking, and recall adapters. See the full package and setup requirements.

Flary Mail

A familiar inbox.
Your own deployment.

Read, reply, compose, and organize mail with your team in the browser. Mailbox changes arrive over WebSockets, while messages and attachments stay in your Cloudflare storage.

Flary Mail runs on Workers, D1, R2, Queues, and a hibernating Durable Object per mailbox. It provides a web inbox; IMAP, POP, and external mailbox synchronization are not included.

Install your team inbox

Ready in the Mail starter

  • Mail on your own domain
  • Inbox, sent mail, drafts, and folders
  • Replies and attachments
  • Team access and live mailbox updates

You operate the app and pay Cloudflare for its usage. Flary does not host your mailbox or manage it for you.

Why Flary

Start with the app.
Build from there.

Choose Flary when you want the setup, app templates, connections, durable threads, files, approvals, and interface brought together. You can use the result or keep building on its TypeScript source.

Compare Flary, Flue, and the Agents SDK

Built on Flue. Built for Cloudflare.

Flue powers Flary’s agent session runtime. Its harness is a good fit when you want to compose agent behavior directly or use another host.

Cloudflare’s Agents SDK also provides durable state, realtime connections, scheduling, tools, and starter apps. Flary’s focus is its own authoring API and an assembled path to an assistant, backend, or team inbox in your account.

For developers

Your product.
Your agent’s tools.

src/flary.ts
import { flary } from "flary";

export const app = flary({
  model: "openai/gpt-5",
});

Explore editable examples using the public package APIs, including integrations for Tracked and Fairway Florist.

Take the first step

Choose what you
want to run.

Start with the guided install. For an existing project, use flary init to add typed functions and agents to the deployment you already have.

Open the install guide

Working from a clone?

git clone https://github.com/rdvo/flary.git
cd flary
npm run setup

The launcher checks dependencies and opens the local AI installer.