Private services: an internal service with no public address
What a private service is, why an internal API or queue consumer should not be reachable from the public internet, and what Voroa offers for this today.
What this covers
A private service runs the same way a web service does, but has no public address. Only your other services can reach it, over the platform’s internal network. You would use one for an internal API that your public front end calls, a service that holds credentials you never want exposed, or anything that should be unreachable from the internet by design rather than by an access check you have to remember to write. The security value is simple: an address that does not exist cannot be scanned, guessed or attacked.
Private services are not available on Voroa today. Every service you create either has a public address or, in the case of a background worker, no inbound network access at all.