Your whole stack, together.
Applications, databases, persistent storage, and background work in one connected project.
Dreamstack Cloud
Deploy your code. Connect your data. Scale your services. Bring the work behind every release into one clear place.
Applications, databases, persistent storage, and background work in one connected project.
Public endpoints for your customers. Private connections for the services behind the experience.
Logs, metrics, environments, and deployment history close to the team that owns the product.
From your repository to the services your customers use, every part has a place. Build, networking, compute, and data work together.
The platform, from end to end
Explore the building blocks for deploying, connecting, scaling, and operating your application.
Bring your code, connect your data, and give every part of your application a place to run.
Run applications from Docker images, GitHub repositories, or local code. Keep web services and background workers in the same project.
Connect PostgreSQL, MySQL, MongoDB, and Redis to your application, with backups alongside your data.
Mount durable storage for files and state that need to survive a release. Track disk usage as your data grows.
Run recurring tasks on a cron schedule, from routine housekeeping to data processing and scheduled notifications.
Start with a reusable stack of services and databases. Customize it for your project or share it with your team.
Manage service settings, shared variables, and references between services without putting secrets in your repository.
Give customers a public entry point and keep communication between your services private.
Publish your application with a service URL and route incoming traffic to the service that handles it.
Connect services through internal networking and service discovery. Keep database and worker connections off the public internet.
Expose services that use protocols beyond HTTP, with configurable ports and connection routing.
Bring your own domain, including wildcard domains, and connect it to your application’s public endpoint.
Secure your domains with managed certificate provisioning and renewal, keeping encrypted connections part of the deployment.
Route web traffic through a managed proxy with TLS termination, load balancing, and DDoS protection.
Grow the resources behind a service, add replicas, and choose where your workloads run.
Adjust CPU and memory to the demands of your workload, giving an existing service more room to work.
Run additional replicas and balance incoming traffic across them as your application serves more customers.
Place workloads in the regions that fit your users and data requirements. Discuss regional capacity with our team.
Bring deployment events, application health, resource usage, and cost into the same conversation.
Search, filter, and share logs from the first build through the running application, including structured JSON output.
Arrange CPU, memory, disk, and network metrics into a view that helps your team understand the system.
Follow a request across services with OpenTelemetry-compatible traces and keep application context close to the investigation.
Set a health endpoint and timeout so deployment readiness reflects the way your application actually works.
Set spending thresholds and usage alerts to keep resource growth and project costs visible.
Choose metric thresholds and notification destinations, including email, Slack, Discord, and webhooks.
Separate environments, preview changes, and make the path back to a working release clear.
Keep production and staging separate. Stage configuration changes and choose which services to deploy.
Review changes in temporary environments tied to GitHub branches and pull requests, with cleanup after the work is merged.
Return to a previous successful deployment, redeploy a service, or adjust its restart policy when a release needs attention.
Connect your own tools to project, service, and deployment workflows through the platform API.
Manage application workflows from your terminal and bring repeatable deployment steps into your development routine.
Keep deployment configuration in versioned TOML or JSON files so the team can review infrastructure changes alongside code.
Private connections for your stack. Identity, infrastructure, and support options for teams with enterprise requirements.
Discuss enterprise optionsConnect team access to your identity provider with SAML authentication and centralized team management.
Review user activity and configuration events to understand who changed what across your projects.
Discuss running your stack within your own VPC and making use of existing cloud infrastructure and credits.
Use encrypted private connections between services and keep access scoped to the resources that need to communicate.
Work with our team on support response targets and contractual SLAs that fit your production requirements.
Discuss isolated compute, dedicated hosts, and regional capacity for workloads that need their own infrastructure.
Choose the setup that fits your project. Compare Cloud plans
Bring your framework or container image. Connect a domain, secure your endpoint, and put your application in front of customers.
Keep databases, caches, and mounted storage close to the services that depend on them.
Run queue consumers, scheduled tasks, and processing workloads alongside your public application.
Give your team a place to review a change before it reaches production, with the stack and configuration it needs.
A practical workflow from the first deployment to the release after it.
Choose a repository, a container image, or your local project. Keep the deployment configuration with the code.
Add services, databases, and volumes. Link them with private networking and shared variables.
Review the build, watch application health, and use logs, previews, and rollbacks as the work evolves.
Early access pricing
Plans are billed per project. Compute, storage, and network usage scale with the services you choose to run.
See plans and comparisonsFor prototypes and personal projects that need a clear route to a live service.
For a small production product with services, workers, and a dependable release routine.
For growing products that need more capacity, environments, and operational visibility.
Early-access plan details may evolve as the platform develops. Contact us for higher-capacity or custom infrastructure needs.
Web applications, APIs, containerized services, background workers, and scheduled jobs. Your stack can include databases, caches, and persistent storage alongside the application.
PostgreSQL, MySQL, MongoDB, and Redis are covered in the platform feature set. Discuss the database, backup, and capacity requirements for your project with our team.
Yes. Custom and wildcard domains connect to public services with managed TLS certificates. Private networking connects the services behind your application, while TCP proxying supports non-HTTP workloads.
Published plans are on the pricing page. For SSO, audit logs, your own cloud environment, dedicated virtual machines, or contractual support requirements, contact our team to discuss a custom setup. Feature availability and capacity depend on your plan and project requirements.
Your next chapter starts here
Bring your applications, data, and team together. Tell us about the project you’re building.
Talk about your projectConnecting to support…
Contact our team