Answer the following questions, in order to determine, if this project is needed for your team or not.
Can my team…
- apply Dark Launching practices ?
- deploy frequently the codebase independently from feature release ?
- confidently deploy to production after the automated tests are passed ?
- perform deployment during normal business hours with negligible downtime?
- complete its work without needing fine-grained communication and coordination with people outside of the team?
- deploy and release its product or service on demand, independently of other services the product or service depend upon?
If your answer yes to most of them, then you can stop here, because adding this service to your stack would not solve too much. else, please continue...
toggler primary goal is to provide a vendor-lock free solution to a wide range of audience.
The API's follow simple conventions, making transition easy to almost any other service
in case the service is not enough for the company/team needs.
The secondary goal is derived from the primary, which is to own the data.
Regardless how and where you use, the ownership of the data belongs to you.
There is no free plan that aims you to lock in by data, or by other means.
If you are satisfied with the service,
then the toggler project did well.