Can I use my own stack and deployment tools?

Yes. Full server access lets you install and configure your software and use your own deployment tools. You are responsible for your application and its dependencies.

What can I automate with the API?

The public API supports operations including instance provisioning and management, metrics and scoped access. The API documentation is the source of truth for available endpoints, permissions and request formats.

Is a Git-based deployment pipeline included?

No. You set up deployment with your own tools. The public API lets you automate supported server operations; see the docs for the available endpoints and permissions.

For the thing you’re building next

From side project to your next big thing.

Run your apps, APIs and background jobs on compute you control. Start with one server, automate the repeat work and leave room for the next release.

Choose your compute Read the API docs

Your stack. Full server access. A documented public API.

One idea. Plenty of possibilities.

Build it your way

Applications

APIs

Background jobs

Compute you controlChoose the resources. Configure your environment.

Full server access
Scoped API tokens
Repeat less. Build more.

A possible development workflow, not a deployment status or an automatic CI/CD service.

What changes for you

Keep your workflow. Lose the unnecessary friction.

A home for the whole stack

Host a web app, serve an API or run background workers. Choose resources for the workload and configure the environment your software needs.

Make security part of the setup

DDoS protection is included. Set firewall rules for your services and use scoped API tokens instead of handing a script unrestricted access.

Turn repeat work into a script

Use the documented API to provision and manage instances, inspect metrics and automate common operations. Keep your preferred tools and workflow.

Make room for what comes next

Start small. Build with the next release in mind.

You do not need a fleet to start building properly. Begin with a suitable instance and make the routine work repeatable as your project grows.

01
Choose the first home for your code
Compare current CPU, memory and storage options against your application’s needs.
02
Set up your environment
Configure access, install your stack and deploy using your own tools.
03
Automate the parts you repeat
Create a scoped API token and use the reference to build your own operational scripts.

Before you make the move

Practical answers about plans, setup and server management.

Can I use my own stack and deployment tools?
Yes. Full server access lets you install and configure your software and use your own deployment tools. You are responsible for your application and its dependencies.
What can I automate with the API?
The public API supports operations including instance provisioning and management, metrics and scoped access. The API documentation is the source of truth for available endpoints, permissions and request formats.
Is a Git-based deployment pipeline included?
No. You set up deployment with your own tools. The public API lets you automate supported server operations; see the docs for the available endpoints and permissions.

Give your next idea somewhere to run.

Choose your first server, open the docs and make it yours.