Show HN: Run globally distributed full-stack apps on high-performance MicroVMs

We're headquartered in Europe, you'll find the legal in our terms :) https://www.koyeb.com/docs/legal/terms

There is a difference between edge and non-edge locations (we call them core): edge locations terminate the TLS connection, do caching, and route traffic to the nearest core location. We explained how this works in this post [1] and this talk [2]. The TLDR is: If this core location is set up to run an instance of your service, it will send it to the right machine in the location. Otherwise, it's going to be routed to the core location where an instance is running.

Data storage can be tied to a location as you're deciding where you're application is running: if you ask us to run an application in Frankfurt, Germany we're not going to move it to the US nor to any other location.

The build engine is tied to GitHub but you can deploy a pre-built Docker container. GitLab has been highly demanded [3], so this is definitely on the list of things we're considering implementing.

Databases should land on the platform in September in early access [4], we're actively working on it.

[1] https://www.koyeb.com/blog/building-a-multi-region-service-m...

[2] https://www.youtube.com/watch?v=IB93WCoroL8

[3] https://feedback.koyeb.com/feature-requests/p/git-driven-dep...

[4] https://feedback.koyeb.com/feature-requests/p/managed-postgr...

For a startup or side projects I doubt I have need for edge computing and using Digital Oceans app services should be good enough. Obviously you would be a contender here but not clearly ahead of DO because the need for edge computing is not apparent for most things. Where as DO sell their own compute and are more established.

On the other hand established companies probably want more control over the infra that a big cloud would give you. You have compliance and DR to think about as well as security questionnaires to fill in.

I am guessing there is a gap in the middle? Something like a one year old startup?

I do like the pricing model. It gives me confidence. You are clearly subsidising the free tier at $5.50/m and there should be no “shocks” that you get on other PaaS where the free tier is redicously generous in some dimensions but then the costs become untenable in other dimensions. With your model the free tier only differs in that there is a free allowance not in how things are measured. Which is good!

I’ve explored running @Edge for performance gains and overall improved user experiences, but always have struggled with services like this (or fly.io or even just running my own VMs) and their data center locations.

Looking at your integrations page, for example, you call out PlanetScale so il use that as an example to illustrate my challenge. Koyeb has a region in SFO. PlanetScale’s closest region is in Oregon. For a database connection, that’s a lot of latency which likely undermines the performance gains of running a service at edge (at least in my use cases).

I’ve evaluated just rolling my own database replication for Edge and it’s not a huge deal but often finding information about data center providers to try and pair data with the compute can be challenging.

So the queries I’d like to pose: Are you able to provide Speedtest endpoints or data center information for collocating other resources near each deployed Koyeb region? Do you plan to offer lower level access to compute to address this kind of use case? Is there another implementation angle to this I am missing?