A shared t.large running free for everyone is generous, but I've seen a lot of "free hosted" services quietly disappear once costs stop feeling small.
What is the plan if the hosting gets too expensive to keep free, especially once outbound traffic from AWS starts adding up? Is there a documented migration path so people who build on gateway will not get stuck?
Good question, we have the export functionality so people can move off easily, but I did not take into account a way to contact domain owners to let them know if we are turning off the server. We have enough AWS credits to run gateway for free (to us) for ~20 months as-is, but I suppose we should make a clearly documented plan for sunsetting the service if we ever decide to do that. Great point, and is something I will mull on.
A shared t.large running free for everyone is generous, but I've seen a lot of "free hosted" services quietly disappear once costs stop feeling small. What is the plan if the hosting gets too expensive to keep free, especially once outbound traffic from AWS starts adding up? Is there a documented migration path so people who build on gateway will not get stuck?
Good question, we have the export functionality so people can move off easily, but I did not take into account a way to contact domain owners to let them know if we are turning off the server. We have enough AWS credits to run gateway for free (to us) for ~20 months as-is, but I suppose we should make a clearly documented plan for sunsetting the service if we ever decide to do that. Great point, and is something I will mull on.
My pleasure, i do agree that a clear doc that will explain how to export and a heads up in case you will decide to close it one day, will sort it out.
[dead]