Editing connection access
Connection settings explain missing choices and ask for your password when you save.
Every shipped change, newest first.
Connection settings explain missing choices and ask for your password when you save.
Choose which apps your assistant can work on, and see what to do when a security check stops a publish.
Shared controls across the dashboard, docs and pricing page, grouped logs, and tables that adapt to narrow screens.
Crash reports recognise common causes, keep the memory advice, and give you a prompt for your own AI assistant.
Free now covers two apps and says what to do when a start does not fit. Free apps show a small Percher icon. Rollback, previews and the 1.0.3 tools are more reliable.
The six npm packages establish the 1.0 licence boundary. The 1.0.1 patch clarifies shared data during previews; shared and toml remain at 1.0.0.
Every active preview is now one click away, and the publish history loads instantly.
Scaffold an app with a database, sign-in, and realtime already wired up, then publish. (The managed-AI part is currently switched off.)
Declare redirects and custom response headers in your toml, applied before a request reaches your app.
A secret URL that rebuilds your app — trigger it from a CMS, a cron job, or CI.
Connect a repo with no config — Percher detects the framework and generates one just for that deploy.
Give CI and coding agents a token scoped to deploy, env, or read-only — optionally bound to one app.
Add `https://mcp.percher.app/mcp` as a custom connector in Claude.ai, Cursor, or Windsurf. OAuth login, no token to paste, and your assistant can operate your apps and deploy connected repos.
The blog and changelog now each have their own RSS feed, so you can follow just the one you want.
New `percher diff` shows what changed between deploys, and `percher export --git` hands you your whole history as a git bundle.
Tell your AI assistant to publish and your app goes live in seconds, no signup. Claim it to a real account whenever you want to keep it.
Share a link to your app's live status and recent deploys — no login, nothing sensitive, revocable any time.
Percher now scans every app image for known vulnerabilities, surfaces them in your Security tab, and emails you only when something critical needs a fix.
New accounts confirm their email and accept the terms before going active, with a one-click resend if the link expires.
Download your whole app — source, config, env keys, and database — as a single archive. No lock-in.
Apps that run migrations or warm a cache on boot can now extend the health-check window in percher.toml.
When you invite someone to an app, they now get an email with the role, what it can do, and a link straight to accept.
Starter gets a full 1.0 vCPU pool, disk pools across paid tiers were resized to match the VPS steps we actually run on, and the app cap was raised on every tier.
Settings → Danger zone now lists everything blocking account deletion before the button is enabled — owned apps, collaborators, in-flight deploys, pending transfers.
Each paid tier now sells a per-account RAM, vCPU, and disk pool that you distribute freely across your apps.
Static sites run on a slim, fast Caddy-based container — quick cold starts and small images.
Node and Bun apps build through a purpose-built pipeline — cold builds in ~15–25s, warm redeploys in ~10–15s.
Browse starter templates at percher.app/new and start one with a single command.
Narrow runtime logs by severity and date range, with shareable URLs that preserve the filter.
percher_publish returns immediately and hands the assistant a wait-for-deploy step, so agents stay responsive during long builds.
Install the Percher GitHub App once — every push deploys, pull requests get preview URLs, and deploy status posts back as a commit check.
A new version goes live only after it passes a health check; the running version keeps serving until the swap completes.
Apps can run multiple container instances, with optional CPU-based autoscaling configured in percher.toml.
Every app's database is backed up nightly and replicated off-site; restore from the dashboard or with percher restore.
Subscribe to deploy events with HMAC-SHA256-signed webhooks and wire Percher into your own automation.
Add password = true to percher.toml and visitors get a branded login page before they reach your site.
Say "publish my app" to your AI assistant — or run bunx percher publish — and your app is live at name.percher.run with SSL.
When an app crashes, Percher detects it, explains common causes and emails you.
The Percher API ships a full OpenAPI spec, and the platform exposes operational metrics in Prometheus format.