# Specific Docs

> Specific enables any coding agent to define infrastructure for the code it writes. Start building locally and deploy to production in minutes.

## Docs

- [Welcome](https://docs.specific.dev/): Specific enables any coding agent to define infrastructure for the code it writes. This lets you start building locally and deploy to production in minutes.

## Get started

- [Quickstart](https://docs.specific.dev/quickstart): Let your agent set everything up, or go from local dev to deployed yourself in about five minutes.
- [Installation](https://docs.specific.dev/installation): Install the Specific CLI and prepare your project.
- [Coding agents](https://docs.specific.dev/coding-agents): Give your coding agent everything it needs to build and deploy with Specific.
- [Why Specific?](https://docs.specific.dev/why-specific): The case for agent-first infrastructure.

## Guides

- [Services](https://docs.specific.dev/guides/services): Define how your code runs and how it connects to everything else, in development and production.
- [Builds](https://docs.specific.dev/guides/builds): Define how your code is built: managed base environments or custom Dockerfiles.
- [Crons](https://docs.specific.dev/guides/crons): Scheduled jobs with tracked runs, logs, and metrics.
- [Secrets and config](https://docs.specific.dev/guides/secrets-and-config): Parameterize sensitive and environment-specific values without hardcoding them.
- [Postgres](https://docs.specific.dev/guides/postgres): Managed PostgreSQL databases, locally and in production.
- [Reshape migrations](https://docs.specific.dev/guides/reshape): Zero-downtime database schema migrations, managed automatically.
- [Real-time sync](https://docs.specific.dev/guides/sync): Stream Postgres changes to clients over HTTP, powered by Electric.
- [Object storage](https://docs.specific.dev/guides/storage): S3-compatible object storage that works with any S3 client.
- [Redis](https://docs.specific.dev/guides/redis): Managed Redis-compatible caching backed by Valkey: one block in specific.hcl, a local instance during specific dev, and a connection URL your existing Redis client already understands.
- [Volumes](https://docs.specific.dev/guides/volumes): Persistent directories that survive deploys and restarts.
- [Managed Temporal](https://docs.specific.dev/guides/temporal): Managed Temporal workflow engines for durable workflows: a local dev server with specific dev, and an auto-provisioned Temporal Cloud namespace in production.
- [Custom domains](https://docs.specific.dev/guides/domains): Serve your services from domains you own, with automatic TLS.
- [Preview environments](https://docs.specific.dev/guides/previews): Temporary copies of an environment for testing changes with real data.
- [Observability](https://docs.specific.dev/guides/observability): Query your environments' logs and metrics with SQL.
- [Alerts](https://docs.specific.dev/guides/alerts): Default alerts on every service, and email notifications when they fire.
- [Jobs](https://docs.specific.dev/guides/jobs): Run one-off commands against a deployed service in production.
- [Frameworks and ORMs](https://docs.specific.dev/guides/frameworks): Specific runs any language and framework through plain environment variables. This page covers the few tools with a known trap: Next.js, Prisma, Drizzle, and Python virtual environments.

## Concepts

- [How Specific works](https://docs.specific.dev/concepts/how-it-works): The mental model: one config file that runs your whole system, locally and in production.
- [Local development](https://docs.specific.dev/concepts/local-development): Run your complete system locally with a single command.
- [Deployments](https://docs.specific.dev/concepts/deployments): From source code to a running production environment in one command.
- [Dashboard](https://docs.specific.dev/concepts/dashboard): Observe and manage your deployed projects, with a local counterpart during development.

## Reference

- [CLI reference](https://docs.specific.dev/reference/cli): Every command in the Specific CLI, grouped by workflow.

## Compare

- [Specific vs Terraform](https://docs.specific.dev/compare/terraform): How Specific compares to Terraform as an alternative for application infrastructure: local development, built-in building blocks, a full deploy pipeline, and no state files.
- [Specific vs Supabase](https://docs.specific.dev/compare/supabase): How Specific compares to Supabase as an alternative: standard Postgres access without an SDK, backend services in any language, full-stack deployment, and an agent-first workflow.
- [Specific vs Convex](https://docs.specific.dev/compare/convex): How Specific compares to Convex as an alternative built on open standards: real PostgreSQL and SQL instead of a proprietary runtime, any backend language, and an agent-first workflow.
- [Specific vs Vercel](https://docs.specific.dev/compare/vercel): How Specific compares to Vercel as an alternative for full-stack apps: long-running services in any language, built-in Postgres, storage, Redis, and real-time sync.
- [Specific vs Railway](https://docs.specific.dev/compare/railway): How Specific compares to Railway as an alternative: the whole stack defined in one agent-writable config file, Docker-free local development, and built-in sync and durable workflows.
- [Specific vs Render](https://docs.specific.dev/compare/render): How Specific compares to Render as an alternative: agent-first infrastructure with a full local dev environment, built-in object storage, real-time sync, and managed Temporal.
- [Specific vs Fly.io](https://docs.specific.dev/compare/fly): How Specific compares to Fly.io as an alternative: an integrated application platform with agent-first config and full local dev, instead of infrastructure primitives you assemble.

## Migrations

- [Migrate from Supabase](https://docs.specific.dev/migrations/supabase): How each Supabase feature maps to Specific: the auto-generated API, row level security, auth, storage, realtime, queues and cron, and what stays the same because it is all Postgres.
- [Migrate from Lovable](https://docs.specific.dev/migrations/lovable): Move a Lovable project to your own coding agent and infrastructure: export the code, replace Lovable Cloud, and keep the app running locally and in production.

## Examples

- [Hello World](https://docs.specific.dev/examples/hello-world): A minimal Node.js HTTP server demonstrating the basics of deploying a service with Specific.
- [Database](https://docs.specific.dev/examples/database): A simple Node.js notes API demonstrating PostgreSQL database persistence with Specific.
- [Database with Sync](https://docs.specific.dev/examples/database-with-sync): A minimal Node.js app demonstrating real-time sync across multiple clients using Specific's PostgreSQL sync engine.
- [Cache](https://docs.specific.dev/examples/cache): A simple Node.js page counter demonstrating how to use Redis caching with Specific.
- [Object Storage](https://docs.specific.dev/examples/object-storage): A simple Node.js file uploader demonstrating how to work with a S3-compatible object storage in Specific.
- [Microservices](https://docs.specific.dev/examples/microservices): A demonstration of how multiple services can communicate with each other using Specific's service reference syntax.
- [Secrets and Configs](https://docs.specific.dev/examples/secrets-and-configs): A simple example demonstrating how to use secrets and configs in Specific for managing sensitive and non-sensitive configuration.
- [Durable Workflows](https://docs.specific.dev/examples/durable-workflows): A task queue application demonstrating how to use Temporal for durable workflows, with a local Temporal server in development and Temporal Cloud in production.
- [Blume Docs](https://docs.specific.dev/examples/blume): Run a Blume documentation site locally and deploy its Node server with Specific.

## Spectest

- [Introduction to Spectest](https://docs.specific.dev/spectest): Spectest runs a full copy of your code and infrastructure in a deterministic test environment and tests it from the outside through browsers, CLIs, APIs, and databases.
- [Get started](https://docs.specific.dev/spectest/get-started): Install the Spectest CLI, log in, and let your coding agent build and run a first full-system test suite for your project.

## Agent resources

- [llms-full.txt](https://docs.specific.dev/llms-full.txt): The full Markdown of every page in one file.
- [Page Markdown](https://docs.specific.dev/index.md): Append `.md` to any page URL to fetch that page as raw Markdown.
- [JSON API](https://docs.specific.dev/api/docs/pages.json): Page index of the JSON docs API; each entry links the page's JSON and Markdown forms. Described by the OpenAPI document at https://docs.specific.dev/openapi.json.
- [MCP server](https://docs.specific.dev/mcp): Streamable HTTP Model Context Protocol server with search_docs, get_page, list_pages, and get_navigation tools, plus every page as a resource. Discovery document: https://docs.specific.dev/.well-known/mcp.json
- [API catalog](https://docs.specific.dev/.well-known/api-catalog): RFC 9727 linkset of the APIs documented here.
- [AI catalog](https://docs.specific.dev/.well-known/ai-catalog.json): ARD manifest of the agent-facing resources on this site (MCP server, skills, APIs).
- [agent-readability.json](https://docs.specific.dev/agent-readability.json): Manifest of every agent-facing artifact on this site.
- [Sitemap](https://docs.specific.dev/sitemap.xml): Every indexable page URL with its last-modified date.