AnySites

Deploy anything.
Instantly.

AnySites is the PaaS that gets out of your way. Push code, get a live URL. Managed databases, custom domains, and auto SSL — all included.

No credit card required · No per-seat fees · Live in < 60 seconds

terminal
$ git push origin main
Enumerating objects: 8, done.
Writing objects: 100% (8/8), done.
Triggered build #42
Cloning repository…
Running build command: npm run build
Build completed in 23s
Container started on port 3001
Live: https://my-app-a1b2c3.anysites.app

Works with your existing stack

Node.jsPythonGoRustBunDenoNext.jsFastAPI

// everything you need

Ship faster. Scale effortlessly.

AnySites handles the infrastructure so you can focus on building.

Git Push Deploys

Push to GitHub or GitLab and your app is live in seconds. Automatic builds, zero configuration.

Managed PostgreSQL

Every project gets a dedicated PostgreSQL database, automatically provisioned and connected via DATABASE_URL.

Custom Domains + SSL

Bring your own domain. Certificates are issued and renewed automatically through Cloudflare, no configuration required.

Environment Variables

Securely manage secrets with AES-256 encrypted environment variables, available during both the build and the running app.

Build & Deploy Logs

Real-time streaming build logs. Know exactly what's happening at every step of your deployment.

Instant Rollbacks

Roll back to a recent deploy in one click — it reuses the already-built image, so it's fast, with zero downtime.

// how it works

From code to live
in three steps.

No DevOps degree required. AnySites takes your code, builds it, and serves it to the world — all in under a minute.

1

Connect your repository

Link your GitHub or GitLab account. Import any public or private repo with one click.

2

Push your code

git push to your main branch. AnySites detects the push, runs your build command, and packages the app.

3

You're live

Get an instant preview URL like my-app-a1b2c3.anysites.app. Add a custom domain whenever you're ready.

Deploy your first app
Dockerfile (only needed for non-Node stacks)
# Node.js projects build automatically —
# no Dockerfile required. Anything else
# (Python, Go, ...) brings its own:
FROM python:3.12-slim
WORKDIR /app
COPY requirements.txt .
RUN pip install -r requirements.txt
COPY . .
EXPOSE $PORT
CMD ["gunicorn", "-b", "0.0.0.0:$PORT", "app:app"]
Built-in
Health-checked deploys
Automatic
Zero-downtime cutover
One click
Rollback
Unlimited
Deployments / day

// before you deploy

Everything you need to know about AnySites.

A practical guide to what the platform does, what you need to provide, and when it is—or is not—the right place to run your application.

Read the deployment docs
01

What specific problem does AnySites solve?

AnySites turns an application repository into a live, maintainable service without requiring you to configure virtual machines, reverse proxies, TLS certificates, deployment scripts, or a separate database platform. It is designed for teams whose application has outgrown a static host or serverless-only workflow, but who do not want to become a full-time DevOps team.

Frontends, APIs, background workers, and PostgreSQL can live under one project and one predictable bill. Git pushes create repeatable releases, while logs and rollback history make production changes easier to understand and recover.

02

What do you need to provide?

Start with a GitHub or GitLab repository containing a working application. Node.js projects (including Next.js) build automatically from a package.json — no extra configuration needed. Any other stack — Python, Go, Rust, or anything else — needs its own Dockerfile committed to the repo; AnySites builds that directly.

  • Git repository and production branch
  • Build and start commands (Node) or a Dockerfile (everything else)
  • Required environment variables
  • A process that binds to the assigned port
  • Optional custom domain
03

How does deployment work?

1

Connect

Import a repository and select the production branch.

2

Configure

Confirm commands, add encrypted secrets, and provision PostgreSQL if needed.

3

Deploy

AnySites builds the release, starts the service, and assigns an HTTPS URL.

Future pushes repeat the same pipeline automatically. Preview URLs let you verify changes before production, and a previous healthy release remains available if you need to roll back.

04

What can you do with the result?

The result is a production-ready HTTPS application, not a downloadable mockup. Share the generated URL with customers or teammates, connect your own domain, use preview deployments for review, attach PostgreSQL through DATABASE_URL, and inspect the full build log for every deploy from the dashboard.

You can use AnySites for SaaS products, AI application backends, APIs, dashboards, internal tools, webhooks, scheduled services, marketing sites, and background workers. As demand grows, move to a larger shared compute pool without changing the deployment workflow.

05

When is AnySites not a good fit?

Results will be poor when the repository cannot build consistently outside a developer laptop, depends on undeclared local files, writes important data only to the container filesystem, or does not bind to the platform-provided port. Applications should keep persistent records in PostgreSQL or durable storage and read configuration from environment variables.

AnySites is also not the first choice for dedicated GPUs, custom kernels, extremely specialized networking, multi-region active-active databases, or compliance programs requiring dedicated infrastructure. Contact us for an Enterprise assessment, or use specialist infrastructure when the workload genuinely needs system-level control.

06

How is AnySites different from related tools?

Compared with Vercel: AnySites focuses on always-on containers, workers, and PostgreSQL with predictable plans and no per-developer seat fee, rather than a primarily serverless, usage-metered frontend cloud.

Compared with Netlify: AnySites is built around long-running full-stack services instead of credit-metered deploys, functions, requests, and bandwidth.

Compared with a VPS: you keep the flexibility of a normal application process, while AnySites handles builds, TLS, routing, releases, logs, and rollbacks. You do not patch or rebuild the operating system yourself.

Compared with raw containers: the platform adds Git automation, domains, managed data services, and a deployment UI around the container runtime.

07

How do you fix common deployment problems?

Start with the build logs: they normally reveal a missing dependency, incorrect command, unavailable environment variable, failed migration, or port mismatch. Reproduce the production build locally from a clean checkout, and never rely on files excluded from Git.

Build fails: verify the runtime version, lockfile, build command, and required system packages.

App will not start: bind to 0.0.0.0 and read the assigned PORT.

Database error: confirm DATABASE_URL, migrations, connection limits, and SSL settings.

Domain not working: check DNS records, remove conflicting entries, and allow propagation time.

New release is unhealthy: inspect its logs and roll back to the previous working deployment.

App is slow: review memory use, database queries, external API latency, and the plan's compute pool.

Open troubleshooting documentation

// simple pricing

Predictable pricing for real workloads.

Static sites, container apps, and PostgreSQL included.

试用
$0 / 7-day trial
  • 1 container app
  • 1 static site
  • 1 PostgreSQL database
  • 1 custom domain
Lite
$9/mo
  • 1 container app
  • 3 static sites
  • 1 PostgreSQL database
  • 3 custom domains
Starter
$19/mo
  • 2 container apps
  • 5 static sites
  • 2 PostgreSQL databases
  • 5 custom domains
Pro
$39/mo
  • 4 container apps
  • 10 static sites
  • 5 PostgreSQL databases
  • 10 custom domains
Business
$79/mo
  • 8 container apps
  • 20 static sites
  • 10 PostgreSQL databases
  • 20 custom domains

Ready to ship?

Join developers who deploy with AnySites. Try every feature free for 7 days. No credit card required.