Take a stack that already works under `flisk up` to Render with that host's own tooling - a `render.yaml` blueprint or dashboard services, with their environment variables. It maps each service.json (ports, health checks, dependencies, env) to production artifacts written for the host, never the local `.autogenerated/` files. Use when the user wants to ship a working Flisk stack to Render. Flisk itself stays local; for Helm, Argo CD or Kustomize pipelines use flisk-helm.
Installs into .claude/skills of the current project.
Are you the author of Flisk Deploy Render?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/flisk-sh-flisk-deploy-render)
---
name: flisk-deploy-render
description: Take a stack that already works under `flisk up` to Render with that host's own tooling - a `render.yaml` blueprint or dashboard services, with their environment variables. It maps each service.json (ports, health checks, dependencies, env) to production artifacts written for the host, never the local `.autogenerated/` files. Use when the user wants to ship a working Flisk stack to Render. Flisk itself stays local; for Helm, Argo CD or Kustomize pipelines use flisk-helm.
license: MIT
compatibility: Requires a working local Flisk stack first. Render dashboard or render.yaml recommended.
metadata:
author: flisk-sh
version: "1.0"
---
# Deploy to Render
Flisk is local-only. This skill covers deploying to Render.
## Workflow
1. Confirm the stack works locally with `flisk doctor && flisk up <stack>`.
2. Extract service contracts from service.json.
3. Create a render.yaml or configure services in the dashboard.
4. Set environment variables and secrets.
5. Deploy and verify health endpoints.
## Guardrails
- Do not deploy local generated files.
- Keep production config separate from local service.json.
