About

Apps born in production, maintained by people who use them

FlyeeClub packages the apps we use to build and run our own products, and keeps them working when AI changes.

What your AI runs when it updates three apps at once
~/products
npx flyee updateproduct-scope 1.4.0 → 1.6.0deploy-check 1.1.0 → 1.2.0landing-copy 2.0.1 → 2.1.03 apps updated. The changelog is in the dashboard.

born in production

Portuguese and English

Principles

What holds for every app in the store

The rules that decide what gets in, how it changes and what the page may say.

Born in production

Every app comes from a product that is live. What breaks there gets fixed here, in a new version.

Upkeep is the product

Access includes the new versions when AI changes, with a public changelog and a checksum on every package.

Only numbers from the database

Prices, seats and counts on the page come from the database. No invented testimonials, no fake counters.

Portuguese and English from day one

The apps, the guides and the changelogs are written in both languages.

Who builds it

Every app here has already run in a real product.

Every FlyeeClub app was built for real work before it joined the store. They are built by Bruno Santana, a product engineer who maintains seven systems in production across health, credit and pharma. The FlyeeClub core is the same one that runs in two of those products.

AI changes every week. Someone has to maintain the apps.

To be clear

What FlyeeClub is and what it is not

It is not

A course, a community or a marketplace

  • A course with a beginning, a middle and an end
  • A networking community
  • A marketplace of third-party apps
  • A service that spends your AI credits

It is

A maintained app store

  • A harness in the AI you already use
  • A store organized by product stage
  • Updates with versions, changelogs and checksums
  • Short guides next to each app

Start with the AI you already have

Ask your AI to install it, and to update when AI changes.