8 comments

[ 2.9 ms ] story [ 23.6 ms ] thread
I'm one of the founders of Replicated, would love your thoughts on what we're building.
This will be such a lifesaver. On-prem is the #1 request we have from larger companies, and we've been offered a good amount of money for it. I always say no, but if it's as easy deploying to Heroku, it'll be a no brainer.
Got excited to see Atlassian listed on the page. Didn't find that Atlassian actually uses "Replicated". Felt sad, because Jira, etc. are a bit of a pain to upgrade.

Am I missing something? Seems like an endorsement by Atlassian or working use case at first glance. Same goes, obviously, with Github and Palantir.

I found the use of those logos disingenuous. At first glance you think "wow, they already have some big name customers", until you realise they are simply examples of companies that provide an on-premise version of their SaaS offering. Not entirely dishonest, but a little sneaky IMHO.
Sounds interesting. Curious about something — if my app relies on cloud services (Amazon S3, Google BigQuery, etc), does Replicated do anything around that? I'm guessing I might need to modify my app a bit to ensure that cloud services endpoints are stored in deploy configuration, and not baked into the code?
We don't provide drop-in replacements for these services, however most have open source compatible alternatives. These are similar changes you would need to make if you were to switch IaaS providers & remove vendor lock-in.
When I landed on the homepage, I wondered, "how much do they really solve the on-prem problem." With respect to that, I thought the video was informative, and the value prop was really clear. I'd be interesting in hearing more about what else Travis had to do to be able to support this integration from their side.

P.S. Say hi if you're in the Startup Cincy Slack team. (Tim Metzner shared this post.)