It works!
by Jérémy LEVYJust finished the creation of the first architecture!
It's a docker-based architecture with CI/CD, auto-scaling, SSL (with auto-renewal), load-balancing and zero downtime deployment.
You will also be able to add a data store (MySQL, PGSQL or MongoDB).
It will only be available on AWS at this time (using Fargate, RDS, DocumentDB, CodeBuild and CodePipeline).
You will be able to create this architecture on your own account, in seconds!
Stay tuned!
-
2
Hey Jérémy! Greetings from pas très loin de chez toi!
Questions: what's your distribution channel? Do you already have customers?
Cheers
-
1
Hey Conrad! Happy to talk to a french founder! 🇫🇷
To answer your questions:
- I plan to follow a bottom-up approach for distribution:
- Targeting makers and developers on IH, HN, PH and Reddit.
- Writing blog posts on Medium, starting with subjects like "How to deploy a complete architecture to host your Symfony/Laravel/Express.js/RoR/whatever app on AWS" for example.
- Making partnerships with local startups incubator and online platforms by offering price reduction.
- I don't have any customers yet, given that Revolv is not released :).
Cheers
-
2
Thanks for your answer!
Nice plan already, this should give you some traffic.
If I take the position of a potential customer (which I could be, obviously!), the main questions I would ask myself are:
- How much would it cost me to migrate to your solution? (time, money, downtime)
- How can I trust your system?
- What do I gain from not building this myself? (this is the worst! But as a developer selling to developers, this is a big issue you have to think about)
Do you already have potential customers?
-
1
Thanks for all these interesting questions!
- How much would it cost me to migrate to your solution? (time, money, downtime)
It depends on the type of architecture you will choose.
For a static website for example, a few minutes.
If you have a web and a database server, you will need a few minutes for architecture creation and the time to migrate your data from your database.
For pricing, we will take a percentage of your AWS bill for the architectures used.
- How can I trust your system?
First, I think trust takes time to build.
When GitHub or GitLab were released, for example, you have to trust an unknown company to store your more important asset: your source code.
I think you have to prove yourself one action after another.
But, in more details:
Yes, you'll have to give us an AWS access key to access your account, but:
-
You could log all API calls made by using AWS CloudTrail.
-
You could revoke the access key at any time directly in your AWS account.
-
There is zero lock-in. We only use raw services (like AWS Fargate or AWS CodeBuild) so you can unsubscribe at anytime. Your architectures will remain perfectly usable. You will only lose access to the advanced features offered by Revolv (GitHub/Slack integration, deploy monitoring and rollback, Healthcheck, Notifications...).
- What do I gain from not building this myself?
You'll gain time (obviously), the convenience to create, replicate (for dev env for example) or destroy a complete architecture in one click and the advanced features that Revolv offers you (GitHub/Slack integration, deploy monitoring and rollback, Healthcheck, Notifications...)
- Do you already have potential customers?
Yes! Many clients that I've worked with as a freelance struggle to create an entire architecture on cloud platforms.
-
2
Interesting answers! I actually have zero experience with deployment on AWS (or any scalable architecture in fact) and I'm quite interested by what this solution can offer.
How far are you from a first release?
-
1
Thanks!
I hope to be able to release it in a few weeks.
You can subscribe here if you want to get early access : https://www.producthunt.com/upcoming/revolv-2
-
-
