Keep a clear public boundary
Web services receive public routes. Private services and databases are reached internally by the applications that need them.
Private networking
A connected stack.
A deliberate public edge.
Your web app can be public while its database and supporting services stay private. Connect Openstead services within the same environment using internal hostnames and application credentials.
Your code. Infrastructure included.
The public web
YOUR PROJECT · SAME REGION
Your applicationPublic web service
PostgreSQLPrivate connection
Internal APINo public endpoint
Private connections between the services in your project.
Internal DNSUse service hostnames
Environment scopeConnect related services together
Private dataNo public database ports
PRIVATE NETWORKING ON OPENSTEAD
Put every connection in the right place.
A full application is more than its public URL. Give each dependency a clear role and connect it without exposing another endpoint to visitors.
Connect applications to their data
Use private connection settings for PostgreSQL, MySQL and Key Value. Keep credentials in the application environment, outside the repository.
Group services by environment
Services in the same environment share their private network. Place the application and its dependencies together when setting up the project.
MADE FOR YOUR STACK
Service names become useful addresses.
Use the private hostname shown in the console instead of a public domain. Your application uses its normal HTTP client or database driver to make the connection.
- Keep the caller and destination in the same environment.
- Database credentials are separate from the network address.
- Application authorization still governs sensitive operations.
One application environmentopenstead / configuration
CONNECTION MAPInternet
└─ web application :443
├─ catalog API :8080
├─ PostgreSQL :5432
└─ Key Value :6379
Worker
├─ PostgreSQL :5432
└─ Key Value :6379An example application topology. Internal service addresses and ports are shown in your console.
PUT IT TO WORK
Built for the work
your application does.
App and database
Connect a public application to a relational database without opening a public database port.
Web app and workers
Share a queue or cache between web services and background consumers.
Internal application APIs
Let a public service call supporting components through their internal addresses.
HOW IT WORKS
Create the services. Connect the dependencies.
Choose the environment
Place the application, database and supporting services in the same Openstead environment.
Use internal connection details
Copy the private hostname, port and credentials from each service into the caller’s environment settings.
Verify the application path
Test the connection from the application and review its logs. Apply authentication and authorization to sensitive internal operations.
Which services can connect privately?
Application services, private services, workers and databases can communicate when they are in the same environment and configured with the correct address and credentials.
Does my database need a custom domain?
No. PostgreSQL, MySQL and Key Value use internal connection details. Custom domains are for the public web services and static sites your visitors access.
Can a static site use a private database connection?
Browser JavaScript runs on the visitor’s device and cannot reach the private network. A static frontend should call an authenticated public API, which connects privately to its database.
Does private networking replace authentication?
No. Use database credentials and application authorization for sensitive operations. Private networking defines the connection path; your application controls access to its data and actions.
MAKE YOUR NEXT MOVE
Make the whole stack work together.
Your code. Infrastructure included.