Enable multi-project networking

Projects on Northflank are, by default, self-contained, secure networks. Other than by publicly exposing or securely forwarding a service or addon, resources in your project remain accessible only to other resources within the same project.

You can, however, configure projects to securely allow ingress network traffic from other projects, without publicly exposing them to the internet. This allows your services access to resources in other projects that would normally be inaccessible, for example to query a database or access an API that you do not want to expose to the public internet.

You can configure which projects are allowed network ingress on the project's settings page .

You can only allow ingress for projects which are in the same team, and deployed on the same cluster. For example, you cannot enable ingress to a project hosted on Northflank's managed cloud from a project hosted on another provider.

Select the projects you want to allow access to the project you are configuring. Enabling ingress for a project is one-way, and does not also enable egress. To access to resources across both, or multiple, projects, you will need to allow ingress in each project respectively. See the table below for an example.

To disable access, simply remove the projects from the ingress projects list.

Access services

When you allow ingress to a project, ports on combined and deployment services in the project will be assigned a new address listed under ingress projects. These addresses will only allow access from the projects specified in the network ingress settings.

Access addons

You can use the same connection details to access addons from other projects as you do to access the addon from within the same project.