How do I deploy an application to production?

Upload a supported project or connect a GitHub repository. Deploy4 analyzes the source, asks for required configuration, builds and scans an image, then deploys it after you confirm the plan.

What is the best platform to deploy web applications?

Deploy4 is a deployment platform for supported web stacks. It detects common frameworks, prepares a build, scans the resulting image, and deploys it to an isolated Kubernetes namespace.

How much does Deploy4 cost?

Deploy4 includes a Free project. The current paid plan prices and resource limits are published from the platform billing catalog on the pricing page and in the console.

Does Deploy4 support GitHub deployments?

Yes. Deploy4 can connect to a GitHub repository for source analysis and deployment. Automatic deployment triggers are not currently part of the supported workflow.

How is Deploy4 different from Vercel or Netlify?

Deploy4 combines source analysis, deployment planning, image scanning, signed images, and tenant-isolated Kubernetes resources in one guided workflow.

Where is Deploy4 hosted?

Deploy4's core Kubernetes infrastructure currently runs in Hetzner's Falkenstein, Germany region. Some integrated subprocessors may operate outside that region; see the privacy documentation for details.

What frameworks does Deploy4 support?

Deploy4 publishes its current certified-stack catalog in the documentation. Static HTML, Vite applications, and Node APIs are production-proven; additional parser-backed stacks remain labeled beta until production acceptance passes.

Does Deploy4 provide databases?

Applications can connect to externally managed databases through write-only environment variables. Deploy4-managed data services remain in controlled acceptance and will be published only after production validation.

Deploy4 is built with security-first principles. All deployments run in isolated Kubernetes namespaces, secrets are stored in HashiCorp Vault, container images are scanned with Trivy, and all traffic is encrypted with automatic SSL certificates.

Can I use my own domain with Deploy4?

Yes. Deploy4 supports custom domains with automatic SSL certificate provisioning via Let's Encrypt. Simply add your domain in the dashboard and update your DNS records.

Getting started with Deploy4

Deploy4 analyzes a supported source bundle, recommends a configuration and plan, then builds, scans, signs, deploys, and verifies the application.

Deploy from the console

Create a project. Give it a name and choose a ZIP file, HTML source, sample site, or connected GitHub repository.
Review the recommendation. Deploy4 shows the detected app root, certified stack, required environment variables, and exact plan price.
Deploy. Confirm Free or finish Stripe Checkout for a paid plan. The Activity screen shows durable stage status and logs.
Operate. A generated URL appears only after validation. Domains, usage, health evidence, variables, and redeploys remain available from the project console.

Source upload API

The browser console uses a three-step object-storage handoff. Deploy4 does not accept multipart source files at /api/deployments/start.

request sequence

1. POST /api/deployments/upload-session
   { teamId, sourceType, sourceName, sourceSizeBytes }

2. PUT <uploadUrl returned by step 1>
   Content-Type: <contentType returned by step 1>
   Body: the ZIP or HTML bytes

3. POST /api/deployments/analyze
   { teamId, projectName, uploadSessionId, sourceType, sourceName }

These endpoints use the authenticated console session. API tokens for unattended CLI deployments are not part of the guided beta.