|
|
|
|
|
|
by AntonCTO
1036 days ago
|
|
|
Congratulations on the launch! It seems very intriguing! I have a some open questions: - Where is the company based and what is the jurisdiction? Probably you forgot to add the imprint :o) - Is there a difference between edge and non-edge locations? - Can data storage be tied to a location? - Is it tied to github or can it be used with self-hosted gitlab? - Is there a rough ETA for databases, especially postgres(-like)? Thanks in advance! |
|
|
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...