Run /
Deploy to a region
You can deploy your code to a specific region by creating a project in that region. This allows jobs or services to be run closer to customers, your development team, or external service for better connectivity.
You cannot change the region of a project after it is created, and all resources deployed in that project will be deployed in that region. Builds, unless configured to run on your own cluster, are performed on Northflank build infrastructure outside your project.
Northflank currently supports the following regions:
| Region | API reference | Global region |
|---|---|---|
| Asia Southeast | asia-southeast | Asia Pacific |
| Europe West | europe-west | EMEA |
| Europe West Netherlands | europe-west-netherlands | EMEA |
| US Central | us-central | Americas |
| US East1 | us-east1 | Americas |
| US West | us-west | Americas |
Contact support@northflank.com to register your interest for regions not listed above.
You can also integrate with other cloud providers to deploy your own clusters, which will allow you to create projects hosted on your chosen cloud provider, in the regions they support.
Network resources across multiple regions
Resources in a project are, by default, inaccessible from other projects. To allow resources in different projects to communicate you can either:
- create a public port, which exposes your service or database to the public internet
- allow network ingress from your other projects which allows you to use private, secure ports as well as TCP and UDP protocols
Next steps
Bring your own cloud to Northflank
Multi-project networking
Configure projects to securely allow ingress network traffic from other projects.
Use Tailscale
Allow secure access to Tailscale devices to resources within your project.
Run an image continuously
Deploy a built image as a continuously-running service.