Regarding your story, I mean wow, that must have been a scary and stressful situation. I am glad you are in a better place now.
487 karma · joined March 18, 2011
Regarding your story, I mean wow, that must have been a scary and stressful situation. I am glad you are in a better place now.
And I wish I could share some pics of my failed ones, I did try my best to differentiate.
Now I am 36 year old and as stated in the post, I am giving yet another shot with https://blanq.io with a hope of succeeding this time.
I have been a solo-dev working on Blanq[1] for more than a year now. It is a powerful link shortening platform that supports custom domains, SSL and traffic routing. I released the API to simply link management for you. The plans are cost-effective and the service is extremely reliable(99.99% uptime).
The backend is Java Spring based with Mysql as DB. To generate docs, I have used Redoc open source tool that relies on Open API spec. I will soon release Zapier integration as well.
For graphs, I have used apex charts that are a pleasure to use. The UI is built on Vue and uses some third party plugins.
Here's an example of analytics https://blanq.io/analytics.html
I am an advocate of privacy and have tried to incorporate as many best practices as possible to avoid identifying users.
I am open to feedback and would love to hear your experience.
[1] https://blanq.io
1. I searched for basic monitoring solutions for actively monitoring the backend and finalized New-Relic. They provide a free plan that is good enough for most startups. I have added a bunch of graphs for system, infrastructure and application monitoring. It keeps me sane and well-informed before things go wrong.
2. On my Digital ocean droplets and database, I have set up Slack alerts that page me in case there is a spike. I have created a free slack workspace just for this and added a different alert ringtone so as to not get confused with other workspaces.
3.I use Freshping to monitor Uptime and again, if things go down, I get email and slack alerts within couple of minutes.
4.I have Rollbar agent running for log monitoring. I get an email alert when there is an exception or error.
5. If I am out for more than half a day, I take my laptop with me.
6. I keep my phone on. Always.
In the last one year, rarely things have gone down. I mean maybe a couple of times.
Things I do so I can sleep properly,
1. I do not deploy before heading out, or on Fridays or at bedtime.
2. My infrastructure has a lot of redundancy meaning, a larger instance than required to handle a spike in case I am unavailable.
3. Database usually breakdown, so have recently migrated to Digitalocean managed database.
Things I am planning to do,
1.Try out Monit to automate some of the tasks.
2. Write down a list of steps or a runbook in case things go wrong. It is easy to forget steps when the production system is down.
[1] https://blanq.io
I recently shut down my free plan and instead introduced Trial on paid plans for my SAAS [1]. Brought in a new entry-level plan that is significantly cheaper to make the transition easier.
As an indiehacker, the free plan allowed me to iron out bugs and improve the overall experience of the platform. But the amount of effort it took to maintain the free plan was enormous so, I shut it down. I informed users about the decision and, I am glad few converted to being paid customers.
The most difficult part was to convert free users into paid ones. I tried everything - Coupons, discounts, emailing customers, lowering the limits, limited offers etc. Nothing really worked.
I have a lot of free time now and I can focus on delivering value to my customers. The server load has also reduced due to the reduction of free requests and database writes/reads.
For a large SAAS company like Slack, Trello etc, it makes sense to have a free plan since you have a lot of resources at your disposal but, if you are a small team or worse alone, then hell no.
[1] http://blanq.io/
As an indiehacker, the free plan allowed me to iron out bugs and improve the overall experience of the platform. But the amount of effort it took to maintain the free plan was enormous so, I shut it down. I informed users about the decision and, I am glad few converted to being paid customers.
I have a lot of free time now and I can focus on delivering value to my customers. The server load also reduced due to reduction of free requests and database writes/reads.
For a large SAAS company like Slack, Trello etc, it makes sense to have a free plan since you have a lot of resources at your disposal but, if you are a small team or worse alone, then no.
What keeps me motivated is how much fun I have working on it. When I wake up every day, I look forward to hearing from my users. It gives me great pleasure knowing a handful of users love my product and use it on a daily basis.
While daily office grind bores me to death, working on my app is exciting.
The other factor is that it costs me $36 per month to run it - so cost-wise I don't mind since its low. I just need another customer to break even.
I don't think anything will change if it grows to a million users. I have not really thought about it.
I will need to double down on marketing efforts in coming days. But I do see there is a need.
I have spent last few months talking to unsatisfied customers of Bitly and following this space and I see a general disappointment with UX, lack of flexibility and high costs associated with the platform.
My service https://blanq.io has tried to address these but I feel there is plenty of space left for more players to enter in. It is relatively easy to get started and scale the service. The barrier of entry is quite low.
But you would need to differentiate your platform - there are like a 1000 clones of Bitly that pretty much do the same.
Running a free URL shortener costs time and money which is why they do it. For my URL shortening service https://blanq.io, I am planning to remove this feature and only support custom domains. Free shortening is highly abused by spam and its a daily battle to be one step ahead of them.
Last week, a single bad user created a phishing link and brought down the entire site for an hour until I was able to restore it.
Lesson learned.
Businesses that I target have set up custom domains and reap more benefit from it.
I eventually plan to retire default shortening domain(blanq.io) and only offer custom domains.
2. Businesses like to pay.
3. Github has been bad lately https://www.theregister.com/2020/07/13/github_takes_some_dow...
1. I looked at https://github.com/nelsontky/gh-pages-url-shortener/blob/mai... and it is a basic script that does nothing more than redirection. A lot of URL shorteners on the web do a lot more. Premium ones can track users and route links based on client.
2. Most of URL shortening audience is non-technical and they usually like to pay and forget about it. Hosting and running your own service is an overhead.
3. Handling traffic at scale is challenging. So, if you have a lot of hits, I would not advise spending time maintaining the service.
4. Github can kill this anytime.
That said, this is neat solution for basic needs.
Would love to hear what you think of it?