The local runtime your AI agent can start, check and fix.
Run your whole app on your machine, from a Compose file or plain commands. Your agent reads its health and logs, and fixes what breaks.
Watch the tour in your browserTry it first. No signup, no global install.
MIT. No telemetry. Releases are signed with Sigstore. Check one yourself
Copied. Paste it in a terminal, then run your own app.
Free, MIT licensed, not a deploy tool. Source
Teams running flisk up on their own code All adopters
This is the real FliskOS interface with sample data. Nothing starts on your machine and nothing leaves your browser. How it was made
This is the live Command Comparer. Search a command to see it next to Compose, Tilt, Terraform and more. Open cmd.flisk.si
This is the live DevEx Roadmap, a community-edited map of local developer tools. Open roadmap.flisk.si
Now run your own app.
Pick where you are starting from. Each path is a few commands.
Every service keeps its ports, names and env values. Nothing starts until you run flisk up.
npm install -g @flisk-sh/fliskcd your-projectflisk import .flisk upCreate the project, add services when you need them, and run them with one command.
npm install -g @flisk-sh/fliskflisk projectflisk upGive Claude Code, Cursor or Codex the Flisk MCP server and skills, then describe the app you want.
npm install -g @flisk-sh/fliskflisk connect claudePrefer pnpm, Bun or a prebuilt binary? See the install options.
Start it. Check it. Fix it.
The same three jobs, from your terminal or from your agent.
Start your whole app from what you already have.
A plain Compose app answered 49 s after flisk import on a clean CI runner. How this was measured
Flisk reads your Compose file. Every service keeps its ports, names and env values.
$ flisk import . $ flisk up --wait
A service that declares a command runs as a local process. Your app's own runtime is all it needs.
{
"appName": "api",
"command": "node server.js",
"port": 4000,
"healthCheckPath": "/health"
}
The wait flag returns once the stack is healthy, so the next step never runs against a half-started app.
$ flisk up --wait
One command gives Claude Code, Cursor or Codex an MCP server, skills and an AGENTS.md.
$ flisk connect claude
Check what is running, and why it is not.
In one recorded agent run on a two-service app, status showed both services unhealthy and logs named the cause, DATABASE_URL is not set. Read the run
Doctor checks your machine first and ranks failing checks by what blocks you most.
$ flisk doctor
In a big project, see only the services that are failing or still starting.
$ flisk status --unhealthy
Read the recent logs of the services in trouble, and skip the rest.
$ flisk logs --unhealthy --tail 50
Confirm the generated files still match your manifests.
$ flisk config verify --json
Fix it without leaving the loop.
In that same run, the agent fixed the code, restarted the stack with down and up, and status showed both services ready. Read the run
Your agent calls these as MCP tools, so it can act on what it reads without you relaying errors.
doctor up status logs down
On the Docker and Tilt path, restart a single service and leave the others running.
$ flisk restart api
Local processes do not reload on save. Stop and start the stack to pick up a change.
$ flisk down $ flisk up
On the Docker and Tilt path, containers update when you save a file.
# edit api/server.js and save $ curl localhost:4310 hello after save
# generated [from service.json]
Your local stack, generated from one file.
One real service from the restaurant example. Pick a file, then hover the marked lines to see why each part is there.
service.json is the one file you write per service. Hover the highlighted lines to see what each part feeds.
A four-layer build generated per service. Layers that change least sit at the bottom, so Docker can reuse them from cache.
One compose file per stack, generated from every service.json in it. You never edit it; Flisk rewrites it when a manifest changes.
Test and coverage settings are generated too, so every backend in the stack starts from the same bar.
{ "$schema": "https://flisk.sh/schema.service.json", "schemaVersion": 1, "appName": "reservation-api", "appType": "backend", "stack": "guest",Identity. Name, kind, and stack. Flisk derives image names, routes, and folder layout from these three values. "port": 4100, "databaseName": "Flisk_restaurant", "dependsOn": ["restaurant-migrator"], "healthCheckPath": "/health"Runtime contract. Port, database, startup order, and health path. These flow into the Dockerfile, the stack compose file, and Traefik.}
# ---- L1: os_base (Golden L1: tdk-restaurant-example-l1:latest) ----FROM tdk-restaurant-example-l1:latest AS l1_os_base# OS dependencies pre-installed in golden L1 imageWORKDIR /app# ---- L1: runtime_env ----# Shared runtime environmentENV NODE_ENV=productionENV BUN_INSTALL_CACHE_DIR=/cache/bunL1 starts from a shared golden base image, so OS packages and the runtime are installed once for the whole stack.# ---- L2: dependency_manifest ----FROM tdk-restaurant-example-l2:latest AS l2_deps_manifestWORKDIR /app# Cache-busting mechanism - change this value to force dependency reinstallARG CACHE_BUSTER=2026-06-25-v1RUN echo "Cache buster: ${CACHE_BUSTER}"# Copy workspace root for monorepo resolutionCOPY package.json ./package.jsonCOPY services/guest/reservation-api/.autogenerated/.npmrc.docker.autogenerated /app/.npmrcCOPY services/guest/reservation-api/.autogenerated/bunfig.docker.autogenerated.toml /app/.bunfig.toml# Copy service manifest files for deterministic dependency layerWORKDIR /app/services/guest/reservation-apiCOPY services/guest/reservation-api/package.json ./package.jsonCOPY services/guest/reservation-api/.autogenerated/.npmrc.docker.autogenerated .npmrcCOPY bun.lock* ./COPY services/guest/reservation-api/.autogenerated/bunfig.docker.autogenerated.toml .bunfig.toml# Diagnostics suppressed (set TILT_DEBUG=true for verbose output)# Install dependencies (quiet by default; set TILT_DEBUG=true for verbose diagnostics)COPY shared-platform-engineering/docker-templates/install-deps.sh /usr/local/bin/install-deps.shRUN --mount=type=cache,target=/cache/bun,sharing=shared chmod +x /usr/local/bin/install-deps.sh && start_ts=$(date +%s) && /usr/local/bin/install-deps.sh && end_ts=$(date +%s) && echo "install-deps duration: $((end_ts-start_ts))s"RUN mkdir -p /app/node_modules/.bunL2 copies only manifests and the lockfile, then installs against a shared cache mount. Editing source code does not touch this layer.# ---- L3: backend_compiler ----FROM tdk-restaurant-example-l3-backend:latest AS l3_backend_buildWORKDIR /app/services/guest/reservation-api# Build argument to skip Infisical setup (for local dev / fast builds)ARG SKIP_INFISICAL_SETUP=0# Reuse resolved dependencies from l2_deps_manifest to avoid reinstalling in L3COPY --link --from=l2_deps_manifest /app/services/guest/reservation-api/node_modules ./node_modules# Bun isolated linker symlinks may resolve through /app/node_modules/.bunCOPY --link --from=l2_deps_manifest /app/node_modules/.bun /app/node_modules/.bun# Copy manifest files for dependency installation (in case L2 is stale)COPY services/guest/reservation-api/package.json ./package.jsonCOPY services/guest/reservation-api/.autogenerated/bunfig.docker.autogenerated.toml ./bunfig.tomlCOPY services/guest/reservation-api/.autogenerated/.npmrc.docker.autogenerated ./.npmrcCOPY services/guest/reservation-api/.autogenerated/tsconfig.docker.autogenerated.json ./tsconfig.jsonCOPY services/guest/reservation-api/.autogenerated/tsconfig.autogenerated.json ./.autogenerated/tsconfig.autogenerated.jsonCOPY services/guest/reservation-api/.autogenerated/*.ts ./.autogenerated/COPY services/guest/reservation-api/src ./srcENV NODE_ENV=productionRUN bun run build# Fix hono/cors subpath import for Bun runtime compatibilityRUN find ./dist -type f -name "*.js" -exec sed -i "s|from 'hono/cors'|from '../node_modules/hono/dist/middleware/cors/index.js'|g" {} + || trueL3 compiles. It reuses the node_modules resolved in L2 instead of installing again.# ---- L3: production_purger ----FROM tdk-restaurant-example-l2:latest AS l3_production_purgerWORKDIR /app/services/guest/reservation-apiCOPY services/guest/reservation-api/package.json ./package.jsonCOPY services/guest/reservation-api/.autogenerated/bunfig.docker.autogenerated.toml ./bunfig.tomlCOPY services/guest/reservation-api/.autogenerated/.npmrc.docker.autogenerated ./.npmrcRUN --mount=type=cache,target=/cache/bun,sharing=shared bun install --production --cache-dir=/cache/bun# Option 2: Aggressive node_modules pruning to reduce size# NOTE: Keep .d.ts files - they are needed for Bun module resolution with subpath exportsRUN find node_modules -type f \( -name '*.md' -o -name '*.ts' ! -name '*.d.ts' -o -name '*.map' -o -name '*.test.js' -o -name '*.spec.js' -o -name 'README*' -o -name 'CHANGELOG*' -o -name 'LICENSE*' \) -deleteRUN find node_modules -type d \( -name '.bin' -o -name 'test' -o -name 'tests' -o -name '__tests__' -o -name 'spec' -o -name 'specs' -o -name '.github' -o -name 'docs' -o -name 'examples' \) -exec rm -rf {} + 2>/dev/null || trueA second L3 stage installs production dependencies only and prunes docs, tests, and source maps.# ---- L4: backend_runtime ----FROM tdk-restaurant-example-l4-backend:latest AS l4_backend_runtimeWORKDIR /app/services/guest/reservation-api# Build argument to skip Infisical setup (for local dev / fast builds)ARG SKIP_INFISICAL_SETUP=0ENV NODE_ENV=productionCOPY --from=l3_production_purger /app/services/guest/reservation-api/node_modules ./node_modulesCOPY --from=l3_production_purger /app/services/guest/reservation-api/node_modules/.bun /app/node_modules/.bunCOPY --from=l3_backend_build /app/services/guest/reservation-api/dist ./distCOPY services/guest/reservation-api/package.json ./package.json# Fix Bun hoisted package symlinks that break when copied to DockerUSER rootCOPY shared-platform-engineering/docker-templates/bun-hoisted-symlink-fix.sh /usr/local/bin/bun-hoisted-symlink-fix.shRUN chmod +x /usr/local/bin/bun-hoisted-symlink-fix.sh && /usr/local/bin/bun-hoisted-symlink-fix.shUSER bunEXPOSE 4000COPY --chmod=0755 shared-platform-engineering/docker-templates/infisical-entrypoint.sh /entrypoint.shENV RESOURCE_NAME="reservation-api"ENV INFISICAL_SECRET_PATH="/services/reservation-api"ENV INFISICAL_TOKEN=${INFISICAL_TOKEN:-}ENV INFISICAL_CLIENT_ID=${INFISICAL_CLIENT_ID:-}ENV INFISICAL_CLIENT_SECRET=${INFISICAL_CLIENT_SECRET:-}ENV INFISICAL_API_URL=${INFISICAL_API_URL:-http://infisical:8080}ENV INFISICAL_PROJECT_ID=${INFISICAL_PROJECT_ID:-}ENV INFISICAL_ENVIRONMENT=${INFISICAL_ENVIRONMENT:-dev}ENV INFISICAL_ALLOW_FALLBACK=${INFISICAL_ALLOW_FALLBACK:-true}ENV RESOURCE_NAME=reservation-apiENTRYPOINT ["/entrypoint.sh"]CMD ["bun", "run", "start"]L4 is the runtime: production node_modules, the built dist folder, and a non-root user.FROM l4_backend_runtime AS productionFROM l4_backend_runtime AS development################################################################################ 🛑 CRITICAL: SYSTEM-GENERATED FILE - DO NOT MODIFY DIRECTLY## ANY MANUAL CHANGES MADE TO THIS FILE WILL BE WIPED ON THE NEXT 'tilt up'.# TO MODIFY THIS CONFIGURATION:# 1. Edit the source generator in: .tilt/topologies/# 2. Or update service.json## Generation Source: golden_docker_generator_v2.L4_generate_orchestrator# Service: reservation-api# Type: Use docker_build(dockerfile_contents=...) in Tiltfile###############################################################################
################################################################################ 🛑 CRITICAL: SYSTEM-GENERATED FILE - DO NOT MODIFY DIRECTLY## ANY MANUAL CHANGES MADE TO THIS FILE WILL BE WIPED ON THE NEXT 'tilt up'.# Generation Source: .tilt/topologies/platform/docker/index.star###############################################################################Every generated file says so at the top and names the generator that wrote it.# =============================================================================# PORT DEFINITIONS - Change these to change ports everywhere# =============================================================================x-backend-port: &backend-port 4100x-frontend-port: &frontend-port 80Ports are declared once as YAML anchors and reused below.# =============================================================================# MEMORY LIMITS# =============================================================================x-nix-any-m1-arm64-memory-limit: &nix-any-m1-arm64-memory-limit deploy: resources: limits: memory: 192M reservations: memory: 64Mx-frontend-memory-limit: &frontend-memory-limit deploy: resources: limits: memory: 64M cpus: '0.15' reservations: memory: 32MMemory limits keep a laptop usable when many services run at once.services: reservation-api: image: guest_reservation-api:dev restart: unless-stopped build: context: ../../../../. dockerfile: services/guest/reservation-api/.autogenerated/Dockerfile.app.autogeneratedEach service builds from its own generated Dockerfile. env_file: - ../../../services/guest/reservation-api/.autogenerated/.env.backend.autogenerated environment: - RESOURCE_NAME=reservation-api - INFISICAL_SECRET_PATH=/services/reservation-api - INFISICAL_TOKEN=${INFISICAL_TOKEN:-} - INFISICAL_CLIENT_ID=${INFISICAL_CLIENT_ID:-} - INFISICAL_CLIENT_SECRET=${INFISICAL_CLIENT_SECRET:-} - INFISICAL_API_URL=${INFISICAL_API_URL:-http://infisical:8080} - INFISICAL_PROJECT_ID=${INFISICAL_PROJECT_ID:-} - INFISICAL_ENVIRONMENT=${INFISICAL_ENVIRONMENT:-dev} - INFISICAL_ALLOW_FALLBACK=${INFISICAL_ALLOW_FALLBACK:-true} - RESOURCE_NAME=guest - PORT=4100 - INSTANCE_ID=0 - NATS_QUEUE_GROUP=guest_backend_svc - TILT_DATABASE_URL=postgresql://tdk_restaurant_example:${DB_PASSWORD}@tdk_restaurant_example_postgres:5432/tdk_restaurant_example_guest?schema=public - TILT_NATS_URL=nats://tdk_restaurant_example_nats:4222 - NODE_ENV=development - DATABASE_URL=postgresql://tdk_restaurant_example:${DB_PASSWORD}@tdk_restaurant_example_postgres:5432/tdk_restaurant_example_guest?schema=public # Per-project escape hatch: set AUTO_MIGRATE=false in the project root .env # to skip Prisma auto-migration at container boot (e.g. while diagnosing a # migration/CLI issue) without touching the generator or any service code. - AUTO_MIGRATE=${AUTO_MIGRATE:-true} - AUTH_MODE=identity-service - IDENTITY_RESOURCE_URL=${IDENTITY_RESOURCE_URL:-None} labels: - "traefik.enable=true" - "traefik.http.routers.reservation-api.rule=Host(`guest.backend.tdk_restaurant_example.local`)" - "traefik.http.routers.reservation-api.entrypoints=web" - "traefik.http.routers.reservation-api.service=reservation-api" - "traefik.http.services.reservation-api.loadbalancer.server.port=4100" - "traefik.http.services.reservation-api.loadbalancer.healthcheck.path=/health" - "traefik.http.services.reservation-api.loadbalancer.healthcheck.interval=10s" - "traefik.http.services.reservation-api.loadbalancer.healthcheck.timeout=5s" - "traefik.http.services.reservation-api.loadbalancer.healthcheck.followredirects=false"Traefik health checks use healthCheckPath from service.json. - "traefik.docker.network=tdk_restaurant_example_traefik-public" - "traefik.http.routers.reservation-api-project.rule=Host(`api.tdk-restaurant-example.localhost`) && PathPrefix(`/api/reservation`)" - "traefik.http.routers.reservation-api-project.entrypoints=web" - "traefik.http.routers.reservation-api-project.service=reservation-api" - "traefik.http.routers.reservation-api-project.middlewares=reservation-api-strip-prefix-project" - "traefik.http.middlewares.reservation-api-strip-prefix-project.stripprefix.prefixes=/api/reservation" - "traefik.http.routers.reservation-api-project.priority=116" - "traefik.http.routers.reservation-api-management.rule=Host(`api.tdk-restaurant-example.localhost`) && PathPrefix(`/api/guest-management`)" - "traefik.http.routers.reservation-api-management.entrypoints=web" - "traefik.http.routers.reservation-api-management.service=reservation-api" - "traefik.http.routers.reservation-api-management.middlewares=reservation-api-strip-prefix-management" - "traefik.http.middlewares.reservation-api-strip-prefix-management.stripprefix.prefixes=/api/guest-management" - "traefik.http.routers.reservation-api-management.priority=121" # Redirect middleware for URL restructuring: old path -> new path - "traefik.http.middlewares.reservation-api-redirect.redirectregex.regex=^`/guest-management/api/v1/(.*)`" - "traefik.http.middlewares.reservation-api-redirect.redirectregex.replacement=`/api/reservation/$$1`" - "traefik.http.middlewares.reservation-api-redirect.redirectregex.permanent=true" networks: - tdk_restaurant_example_traefik-public - tdk_restaurant_example_backend - tdk_restaurant_example_database - tdk_restaurant_example_infisical-network healthcheck: test: ["CMD", "curl", "-f", "--max-time", "5", "http://localhost:4100/health"] interval: 10s timeout: 5s retries: 6 # STORY 4 FIX: 30s grace period to prevent 504 errors during startup # Services get 30s to initialize before health checks begin start_period: 30s # Note: depends_on removed - Tilt manages service startup order deploy: resources: limits: cpus: '0.5' memory: 512M reservations: cpus: '0.2' memory: 256M reservation-app: image: guest_reservation-app:dev build: context: ../../../../. dockerfile: services/guest/reservation-app/.autogenerated/Dockerfile.app.autogenerated target: production <<: *frontend-memory-limit env_file: - ../../../services/guest/reservation-app/.autogenerated/.env.frontend.autogenerated environment: - VITE_APP_ENV=development labels: - "traefik.enable=true" - 'traefik.http.routers.reservation-app.rule=Host(`reservation-app.localhost`) || (Host(`app.tdk-restaurant-example.localhost`) && PathPrefix(`/reservation-app`)) || (Host(`localhost`) && PathPrefix(`/reservation-app`))' - "traefik.http.routers.reservation-app.entrypoints=web,websecure" - "traefik.http.routers.reservation-app.priority=116" - "traefik.http.routers.reservation-app.middlewares=reservation-app-strip-prefix" - "traefik.http.middlewares.reservation-app-strip-prefix.stripprefix.prefixes=/reservation-app" - "traefik.http.services.reservation-app.loadbalancer.server.port=80" - "traefik.docker.network=tdk_restaurant_example_traefik-public" networks: - tdk_restaurant_example_traefik-public - tdk_restaurant_example_backend healthcheck: test: ["CMD", "wget", "--quiet", "--tries=1", "--spider", "http://127.0.0.1:80"] interval: 10s timeout: 5s retries: 3 # STORY 4 FIX: 30s grace period to prevent 504 errors on startup start_period: 30snetworks: tdk_restaurant_example_traefik-public: external: true tdk_restaurant_example_backend: external: true tdk_restaurant_example_database: external: true tdk_restaurant_example_infisical-network: external: true
///////////////////////////////////////////////////////////////////////////////// 🛑 CRITICAL: SYSTEM-GENERATED FILE - DO NOT MODIFY DIRECTLY//// ANY MANUAL CHANGES MADE TO THIS FILE WILL BE WIPED ON THE NEXT 'tilt up'.// TO MODIFY THIS CONFIGURATION:// 1. Edit the source generator in: .tilt/topologies/// 2. Or update service.json//// Generation Source: Vite.Vite.backend()// Service: reservation-api// Type: Backend (Vitest)///////////////////////////////////////////////////////////////////////////////The header names the generator, the service, and how to change the output: edit service.json, not this file.import path from 'node:path';import { defineConfig } from 'vitest/config';export default defineConfig({ resolve: { alias: { }, }, test: { coverage: { all: true, exclude: [ 'node_modules/**', 'dist/**', 'docs/**', 'src/tests/**', 'src/**/*.test.ts', 'src/**/*.spec.ts', 'src/**/*.d.ts', 'src/test-*.ts', 'prisma/**', '**/*.config.{ts,js}', '**/coverage/**', ], include: ['src/**/*.{ts,js}'], provider: 'v8', reporter: ['text', 'json', 'html', 'lcov'], thresholds: { branches: 70, functions: 70, lines: 70, statements: 70, },Coverage counts all source files and fails under 70 percent on any axis. }, deps: { inline: [], }, environment: 'node', exclude: ['node_modules', 'dist', 'docs/node_modules', '**/tests/e2e/**'], globals: true, include: ['src/**/*.{spec,test}.{ts,js}'],Unit tests run in Node with globals; end to end tests are excluded. },});
Numbers you can rerun.
A plain Compose app (a Node API and Postgres) answered 49 s after flisk import on a clean Ubuntu CI runner, images pulled and built from scratch, install not counted. Run · Claim details.
Stability: 1.x local dev. Generated files are a contract; verify with flisk config verify. Core CLI is MIT and needs no key. Premium is optional.
Who uses Flisk
Teams that run flisk up on their own code. Listed with their consent in ADOPTERS.md.
on npm
Simple apps run as plain processes
Give a service a command in its service.json and flisk up starts it as a local process on your machine. All you need is the flisk CLI and your app's own runtime, such as Node.js, Python, Go or Bun. It suits the first apps an AI agent builds: an API, a website, a worker.
{"appName": "api","appType": "backend","command": "node server.js","port": 4000,"healthCheckPath": "/health"}
flisk up
on npm
Your agent knows Flisk from the first prompt
flisk project now writes 12 Flisk skills for Claude Code (.claude/skills) and for Codex, Cursor and others (.agents/skills), plus a short AGENTS.md that points at them. Files you already have are never overwritten, and --no-agent-skills skips the step.
flisk project
on npm
See each service come up
While flisk up waits, it reports each service as waiting, building, starting, ready or failed, with an N/M ready count. A failed service is named with a pointer to flisk logs -s <name>. In CI or a pipe it prints one plain line per change instead.
flisk up
on npm
Doctor tells you what to fix first
After its checks, flisk doctor prints a Fix first list: failing checks ordered by how much they block you, with one command per line that works on your platform. Warnings come after hard failures, and --json gains the same list.
flisk doctor
on npm
Find what is broken in a big project
flisk status groups services under their stack with a healthy count for each. Add --unhealthy to status or logs to see only failing or pending services; it says so when everything is healthy.
flisk status --unhealthy
More from Flisk.
Other products from the team behind the CLI.
Run your app
Publish and get found
Compare and learn
What Flisk does not do.
The limits first. Each line links to the file that says it.
- Not a deploy tool. It runs your app on your machine. Production stays on Helm or whatever you use now. Claims and evidence
- Plain processes do not reload on save. A service run as a local process needs a stop and start to pick up a change. Container stacks live-update. Quickstart
- Container images are pinned by version tag, not digest. The golden image pull checks no signature. Security notes
- The signature covers the checksums, not each binary. There is no SBOM yet. How to verify a release
- No outside security audit. What was checked, and what was not, is listed line by line. Assurance case
- Two maintainers, no paid support. Fixes go into the latest release. We aim to reply within one working day. What to expect
Honest answers
The same answers we give in engineering reviews.
We need Kubernetes for production
What about CI/CD?
Is 100 services locally realistic?
/health fixture has 100 small generated services (about 20 lines each) that all became healthy through Traefik in 472 s on a clean CI runner, images built from scratch (the run). It is a scale fixture, not a real ERP product. Real services with real dependencies use more memory. Selective startup runs only what you're working on, and golden L1–L4 layers keep rebuilds near-instant. The discovery daemon regenerates only what changed. Our daily driver is a 14-service stack on a 16 GB M1 MacBook, and it performs superbly; the same engine runs a 27-service monorepo every day.Priced against what it replaces
Core stays free, and most teams should stay on free. Premium is a separate key for the extras above; no key required to run flisk up. See what waiting costs.
The full CLI, MIT-licensed, with no license key required.
flisk up, scaffold, Traefik, Postgres, Tilt live update, golden layers- Playwright, C4 and AGENTS.md, if you generate them in your repo
- No key required to run the core CLI
- Community support
Unlocks the paid extras and gives your team a human on the other end.
- Everything in Free
- Verdaccio private npm registry, DDD scaffold and Sablier idle stop
- Ready-made Playwright, C4 and AGENTS.md implementations, downloaded with your key
- Up to 100 project IDs per license key
- Priority support, next business day
- Onboarding session for your stack
Need SSO, air-gapped, or an SLA? Pick Enterprise in the license request below — custom pricing.
How $17 compares
Gitpod starts at $20/mo plus compute. Codespaces runs $60–150 per dev per month at full-time usage. Flisk Premium is $17 flat — compute is your machine.
Coder and Okteto gate RBAC and SSO behind "contact sales". So does Flisk: SSO is on Enterprise, at custom pricing. Premium is the self-serve plan for the extras listed above.
Flisk's core is free and MIT, and stays that way. Sponsors pay for the work behind it: releases, the demo that must always run, and answers to your issues.
Sponsor Flisk on GitHubGet your
Premium license.
Core stays free. Premium is a separate key for the extras above; no key required to run flisk up. Need SSO, air-gapped, or an SLA? Pick Enterprise.
Request a license
See it run on your machine.
Try it first. No signup, no global install.
MIT. No telemetry. Releases are signed with Sigstore. Check one yourself
Copied. Paste it in a terminal, then run your own app.




