claude-skills

Preview Ops

Infrastructure from a sentence. Preview environments for every PR.
The gap between "I have an idea" and "it's running in production" is one prompt.

---

What is Preview Ops?

Preview Ops is an AI-native infrastructure platform that does two things no other tool does at the same time:

1. Infrastructure from a prompt. Describe what you want in plain English. Preview Ops provisions the entire stack -- frontend, backend, database, cache, cron jobs, queues, DNS, SSL -- wires it together, deploys it, and hands you a live URL. No Dockerfiles. No YAML. No dashboard. One sentence, full stack, live in seconds.

2. Preview environments for every PR. Every pull request gets a complete production clone -- frontend, backend, database seeded with test data, isolated network, custom subdomain, SSL. One config file. Works across any combination of cloud providers. Torn down automatically on merge.

These two capabilities share a single engine: an AI agent that understands infrastructure the way a senior DevOps engineer does, but executes in seconds instead of days.

---

The Problem

The cloud industry is built on an assumption: someone on your team knows how to configure infrastructure.

That assumption creates a bottleneck in every organization. Designers can't ship prototypes. PMs can't validate ideas without filing a ticket. Junior developers spend days learning platform-specific config before they write a single line of product code. Solo founders choose between learning Kubernetes and shipping their product.

Preview environments are worse. Every team wants them. Nobody wants to build them. Vercel gives you frontend previews. Railway gives you backend previews. But full-stack previews -- frontend + backend + database + seeded data + wired together + SSL + custom subdomain + auto-teardown -- require custom infrastructure that costs six figures to build internally.

Preview Ops eliminates both problems with a single agent.

---

How It Works

Prompt-to-Production

$ preview-ops deploy "Next.js app with Postgres, Redis cache, 
  Stripe checkout, and a cron job that scrapes pricing data every hour"

Analyzing prompt...
  -> Framework:    Next.js 15 (App Router)
  -> Database:     PostgreSQL 16 (provisioning on Neon)
  -> Cache:        Redis 7 (provisioning on Upstash)
  -> Payment:      Stripe Checkout (webhook endpoint scaffolded)
  -> Cron:         Pricing scraper (registered, interval: 1h)
  -> Region:       us-east-1 (auto-selected, lowest latency to origin)

Provisioning infrastructure...
  [1/6] PostgreSQL instance       ............ done (3.2s)
  [2/6] Redis cluster             ............ done (1.8s)
  [3/6] Edge runtime              ............ done (2.1s)
  [4/6] Cron scheduler            ............ done (0.4s)
  [5/6] SSL certificate           ............ done (1.1s)
  [6/6] DNS propagation           ............ done (0.3s)

Wiring services...
  -> DATABASE_URL           injected
  -> REDIS_URL              injected
  -> STRIPE_SECRET_KEY      placeholder (add in dashboard)
  -> STRIPE_WEBHOOK_SECRET  auto-configured
  -> CRON_ENDPOINT          registered at /api/cron/scrape

Deploying to edge...