UrlyUp doesn't run your code directly on macOS. Each app gets its own isolated space, built on Apple's Virtualization framework, and everything you host stays inside it.
Your app runs inside the UrlyUp Mac app, so it has the same limits macOS puts on any app you install. UrlyUp passes traffic from your public URL to it. With Live App on, a cloud copy answers on the same URL whenever your Mac is offline.
Your public URL is served from one edge host in the US East, connected directly to a Tier-1 backbone rather than through a rented transit provider. Response times from each region are about what the physical distance allows.
No. UrlyUp doesn't open any ports on your Mac. The public URL is an encrypted connection that ends inside the Runner's isolated space, so traffic reaches your Runner without going through your Mac's own network setup.
With Live App on, your Runners stay up even when your Mac is offline. Without it, they're up while your Mac is awake and hosting is on. If you want them always on without Live App, keep the Mac awake. A Mac mini on a shelf works well for this.
It's the only account step. Apple confirms who you are but shares very little with us, and you can hide your email if you want. Knowing each account belongs to a real person lets us deal with abuse on the network. It also means there's no separate password to manage.
It is served from one edge host in the US East on a Tier-1 backbone. Europe measured 79-103 ms and Singapore about 222 ms, which is normal for the distance.