robots.txt
See which AI crawlers other sites block →# As a condition of accessing this website, you agree to abide by the following
# content signals:
# (a) If a Content-Signal = yes, you may collect content for the corresponding
# use.
# (b) If a Content-Signal = no, you may not collect content for the
# corresponding use.
# (c) If the website operator does not include a Content-Signal for a
# corresponding use, the website operator neither grants nor restricts
# permission via Content-Signal with respect to the corresponding use.
# The content signals and their meanings are:
# search: building a search index and providing search results (e.g., returning
# hyperlinks and short excerpts from your website's contents). Search does not
# include providing AI-generated search summaries.
# ai-input: inputting content into one or more AI models (e.g., retrieval
# augmented generation, grounding, or other real-time taking of content for
# generative AI search answers).
# ai-train: training or fine-tuning AI models.
# use: how AI systems may consume the content (immediate, reference, or full).
# ANY RESTRICTIONS EXPRESSED VIA CONTENT SIGNALS ARE EXPRESS RESERVATIONS OF
# RIGHTS UNDER ARTICLE 4 OF THE EUROPEAN UNION DIRECTIVE 2019/790 ON COPYRIGHT
# AND RELATED RIGHTS IN THE DIGITAL SINGLE MARKET.
# BEGIN Cloudflare Managed content
User-agent: *
Content-Signal: search=yes,ai-train=no,use=reference
Allow: /
# Training crawlers
User-agent: Amazonbot
Disallow: /
User-agent: Applebot-Extended
Disallow: /
User-agent: Bytespider
Disallow: /
User-agent: CCBot
Disallow: /
User-agent: ClaudeBot
Disallow: /
User-agent: Diffbot
Disallow: /
User-agent: Google-Extended
Disallow: /
User-agent: GPTBot
Disallow: /
User-agent: omgili
Disallow: /
User-agent: anthropic-ai
Disallow: /
User-agent: Claude-Web
Disallow: /
User-agent: cohere-ai
Disallow: /
User-agent: MistralAI-Training
Disallow: /
User-agent: meta-externalagent
Disallow: /
User-agent: GoogleOther
Disallow: /
User-agent: Baiduspider
Disallow: /
User-agent: PetalBot
Disallow: /
User-agent: AwarioSmartBot
User-agent: AwarioRssBot
Disallow: /
User-agent: Google-CloudVertexBot
Disallow: /
User-agent: QualifiedBot
Disallow: /
User-agent: Cotoyogi
Disallow: /
User-agent: ICC-Crawler
Disallow: /
User-agent: atlassian-bot
Disallow: /
User-agent: FishBot
Disallow: /
User-agent: BorderxBot
Disallow: /
User-agent: NavuBot
Disallow: /
User-agent: SemrushBot-SWA
Disallow: /
User-agent: WARDBot
Disallow: /
User-agent: magpie-crawler
Disallow: /
User-agent: KimiBot
Disallow: /
User-agent: CitibotSiteCrawler
Disallow: /
# END Cloudflare Managed Content
User-agent: *
Allow: /
Disallow: /imprint
Disallow: /privacy-policy
# Canonical sitemap URL (no trailing slash)
Sitemap: https://vela.run/sitemap.xml
# Content Signals — AI content usage preferences (https://contentsignals.org/)
Content-Signal: ai-train=yes, search=yes, ai-input=yes
llms.txt
Compare with other sites' llms.txt files →# Vela
> Vela is a PostgreSQL data platform that gives teams instant database branching via copy-on-write, PITR, and BYOC deployment — built on simplyblock enterprise distributed block storage (NVMe/TCP and NVMe/RoCEv2).
## Products
- [Database Branching](https://vela.run/database-branching/): Copy-on-write database branches for development, QA, migration testing, and AI agent workflows — created in seconds with no full-copy overhead.
- [Database Cloning](https://vela.run/database-cloning/): Instant database clones for seeding environments, load testing, and data exploration without duplicating storage.
- [Unified Postgres](https://vela.run/unified-postgres/): Single Postgres platform covering branching, PITR, HA, and BYOC deployment — replacing fragmented toolchains.
- [Postgres BaaS](https://vela.run/postgres-baas/): Managed PostgreSQL as a service with BYOC deployment, production-grade branching, and no vendor lock-in.
- [Sandbox](https://vela.run/sandbox/): Free interactive Postgres sandbox at demo.vela.run for evaluating branching and cloning without an account.
- [How Vela Works](https://vela.run/how-vela-works/): Architecture overview — NVMe/TCP block storage, copy-on-write snapshots, Kubernetes-native Postgres operator, and BYOC deployment model.
- [Branch Per PR](https://vela.run/branch-per-pr/): Automated database branch provisioning tied to pull request lifecycle for CI/CD pipelines.
- [Pricing](https://vela.run/pricing/): Pricing tiers including a free sandbox and BYOC plans for teams deploying in their own cloud account.
## Use Cases
- [Vela for AI Applications](https://vela.run/vela-for-ai-applications/): Isolated Postgres branches for AI agent workflows, RAG pipelines, and LLM-driven data tasks — consistent snapshots, no shared state.
- [Vela for CI/CD Testing](https://vela.run/vela-ci-cd-testing/): Per-PR database branches that spin up and tear down automatically, eliminating shared staging bottlenecks.
- [Vela for Enterprises](https://vela.run/vela-for-enterprises/): BYOC deployment in AWS, GCP, or Azure for enterprises that require data residency and compliance control.
- [Vela for Startups](https://vela.run/vela-for-startups/): Fast Postgres provisioning with branching workflows that scale from prototype to production.
- [Vela for Fintech](https://vela.run/vela-fintech/): Isolated database branches for financial data workflows requiring audit trails, PITR, and strict data separation.
- [Vela for E-Commerce](https://vela.run/vela-ecommerce/): Database branching for catalog updates, A/B testing, and safe schema migrations in e-commerce Postgres environments.
## Comparisons
- [Neon Alternative](https://vela.run/neon-alternative/): Vela vs Neon — BYOC deployment vs serverless-only, copy-on-write branching performance, and pricing comparison.
- [Supabase Alternative](https://vela.run/supabase-alternative/): Vela vs Supabase — self-hosted Postgres with database branching versus Supabase's managed platform.
- [Vela vs RDS](https://vela.run/vela-vs-rds/): Vela vs Amazon RDS — branching, cloning, cost, and BYOC deployment compared to managed RDS.
- [CloudNativePG Alternative](https://vela.run/postgres-operator/cloudnativepg-alternative/): Vela vs CloudNativePG operator — branching, cloning, and platform features beyond base operator capabilities.
- [Zalando Alternative](https://vela.run/postgres-operator/zalando-alternative/): Vela vs Zalando Postgres Operator — feature and operational comparison.
- [Crunchy PGO Alternative](https://vela.run/postgres-operator/crunchy-pgo-alternative/): Vela vs Crunchy Data PGO — branching and developer experience comparison.
- [StackGres Alternative](https://vela.run/postgres-operator/stackgres-alternative/): Vela vs StackGres — Kubernetes Postgres operator comparison with branching focus.
## Resources
- [Blog](https://vela.run/blog/): Technical articles on Postgres branching, AI data infrastructure, CI/CD workflows, and platform engineering.
- [Glossary](https://vela.run/glossary/): Postgres and data platform terminology — branching, PITR, copy-on-write, BYOC, agent-ready Postgres, and related concepts.
- [User Guides](https://vela.run/user-guides/): Step-by-step guides for getting started with Vela, creating branches, and integrating with CI/CD pipelines.
- [Articles](https://vela.run/articles/): In-depth articles on open source Postgres tooling, BaaS comparisons, and cloud Postgres strategies.
- [Documentation](https://docs.vela.run/): Full platform documentation covering installation, configuration, API reference, and Kubernetes operator setup.
- [Demo](https://demo.vela.run/): Live interactive Postgres sandbox for evaluating Vela branching and cloning without a deployment.
## Key Facts
- Built on simplyblock enterprise distributed block storage (NVMe/TCP and NVMe/RoCEv2) for sub-second branch and clone creation via copy-on-write
- BYOC (Bring Your Own Cloud) — deploys into your own AWS, GCP, or Azure account; data never leaves your infrastructure
- Kubernetes-native Postgres operator — cloud-agnostic, compatible with EKS, GKE, AKS, and self-managed clusters
- Core feature: database branching — isolated, production-like Postgres branches created in seconds without full data copies
- Supports PITR (Point-in-Time Recovery) for precise restore to any transaction
- AI-ready Postgres — branches per agent, consistent snapshots for RAG pipelines, no shared staging databases
- Free sandbox available at demo.vela.run — no account required
- Fork of open source Supabase stack with production-grade branching and BYOC deployment added
- Postgres BaaS with no vendor lock-in — standard Postgres wire protocol, portable workloads
- Contact: hello@vela.run
## Contact
- Website: https://vela.run
- Documentation: https://docs.vela.run/
- Demo / Sandbox: https://demo.vela.run/
- Contact: https://vela.run/contact/
- Email: hello@vela.run