Can I run Feasible myself?

Yes. It’s the same build we run, with everything switched on. The full walkthrough is on self-hosted analytics.

cp .env.sample .env        # set FEASIBLE_APP_HOSTED=false
./feasible db migrate
./feasible account create --email you@example.com --name "Your name"
./feasible serve

account create prints a generated password once - generated rather than typed, so it never lands in your shell history or a process list.

There’s no cut-down edition. No Community build with the good parts removed, no license key, no feature flag that turns off the API or funnels or raw export. The API has no plan check in it at all - not one you could switch on, none written. Goals, funnels, custom properties, webhooks, the MCP server, teams, sharing, exports: all of it, free.

Setting FEASIBLE_APP_HOSTED=false changes two categories of thing, and neither is a feature:

• Billing never starts. No usage metering, no lifecycle sweeper, no account locks, even if payment credentials are sitting in the environment.
• Public signup is off. You create accounts from the machine with the database, so exposing the login page to the internet doesn’t let strangers in. Invited team members still accept invitations normally.

It defaults to true, so a missing setting fails in the safe direction rather than the embarrassing one.

Two things to be about. Migrations never run automatically - db migrate is a command you type, on purpose, because a binary that migrates your database on boot will eventually do it at the worst moment. And you’re the operator now: backups, TLS, upgrades and the pager are yours.

What it costs to run · the license · hosted versus self-hosted