Flisk vs LocalStack, Supabase CLI and Firebase emulators

These emulate cloud services locally. Flisk starts Postgres, NATS and Traefik beside your app.

Task Flisk Local dev stack LocalStack Local AWS Supabase CLI Local backend stack Firebase emulators Local Google services
Set up a project
Different job, closest command.
lstk setup aws

Only writes an AWS CLI profile, no project files

Start the local services
flisk up

Also starts your app

Stop them
No equivalent

Runs until manually terminated, there is no stop command

Check status
No equivalent

Use curl localhost:4400/emulators to list running emulators

Read logs
No equivalent

Emulator UI has a Logs tab, --log-verbosity limits output

Show service URLs
Different job, closest command.
lstk status

Shows the endpoint as host:port, not per-service URLs

supabase status

Prints the API, DB and Studio URLs

No equivalent

Emulator UI defaults to port 4000, other ports are in the CLI log

Choose which services run
flisk config enable-infra monitoring

Optional services only, such as monitoring

No equivalent

Set SERVICES in an env profile in config.toml

supabase start -x studio

Excludes the named containers at start

firebase emulators:start --only firestore
Reset the data
lstk reset

Clears in-memory state, AWS emulator only

supabase db reset

Database only, reapplies migrations and seed

No equivalent

Firestore emulator clears data on shutdown, restart without --import

Diagnose the setup