Skip to main content

Pagifier

Deploy to Kubernetes with one file. No Dockerfiles, no Kubernetes YAML, no Helm charts, no nginx configs. You write pagifier.toml; Pagifier builds the image, generates the manifests, and runs your app.

The whole developer experience is this:

pagifier.toml
version = 1
name = "my-app"
template = "react-static"
environment = "prod"
ingress = "my-app.company.com"

(Prefer YAML? pagifier.yaml works identically — Pagifier accepts both, TOML first.)

zip -r app.zip . && curl -H "Authorization: Bearer $PAGIFIER_TOKEN" \
  -F config=@pagifier.toml -F archive=@app.zip \
  "https://pagifier.company.com/v1/applications/my-app/environments/prod/deployments?wait=true"
{"phase":"Building"}
{"phase":"Available","url":"https://my-app.company.com","done":true,"success":true}

That's it. Behind that one call: an in-cluster image build, security-hardened workloads, TLS ingress, health checks, autoscaling, and a rollback point.

Pick your path​

I want to…Go to
Deploy my app (my company runs Pagifier)Getting started — 5 minutes
Follow a complete exampleDeploy a static site · Deploy an API · Monorepo
Run Pagifier myself (laptop or cluster)Installation — includes building from source
Look something uppagifier.yaml reference · REST API

The rules (there are only three)​

  1. Everything is explicit. Pagifier never reads package.json, never guesses ports, never detects frameworks. If something's missing, you get an error that says exactly what and where.
  2. Templates carry the boring parts. Your platform team publishes templates (react-static, nestjs, go-api, …) with the build commands, images, and caching already right — your file only says what's unique about your app. Anything a template sets, you can override.
  3. Every deploy is a rollback point. Uploads create immutable releases; rolling back is instant and never rebuilds.

What you get without asking​

Zero-downtime rollouts · TLS by default · hardened containers (non-root, read-only, no capabilities) · network policies · canary releases gated on real error rates (in prod, if your platform enables it) · preview environments per pull request · a web console · full audit history.