Hi Pēteris! Tell me a little about your background and what you're working on.
Hello! I'm Pēteris Caune, a guy from Rīga, Latvia. I'm 36, married, and have a two-year-old daughter and three-month-old son. For almost 10 years now, I've been working remotely from my home office. It's getting more challenging now with small kids around, but I still enjoy having a flexible schedule and no commute.
I'm working on Healthchecks.io, a monitoring service for cron jobs, background services, and scheduled tasks. It works by listening for HTTP "pings" from the monitored services. When it doesn't hear from a service for a configurable amount of time, it sends an alert.
Healthchecks.io is used mostly by development teams to track their various automated processes. It is also popular among homelab enthusiasts. People also come up with unconventional use cases like "Slack alerts when nobody has cleaned the office coffee maker for a while."
What motivated you to get started with Healthchecks.io?
At my "day job" I had a growing number of small background services — things like backups and data import tasks — where monitoring would have been nice to have. This was back in 2015. There were already services doing this style of monitoring: DeadMansSnitch and the recently launched Cronitor. Feature-wise they looked good, but I could not quite justify their pricing for monitoring my non-critical services.
I kept circling back to the idea of building it myself. I had expertise in building web applications and some spare time. I thought I might enjoy a side project where I would get to make all the decisions.
I was also annoyed that I could not use the existing services due to their pricing. So I set a challenge to build a service that was as good or better than the existing options with a useful free tier and affordable paid tiers, but still self-sustaining.
Over time this expanded into doing more and more things the "wrong way." I decided to make the code open source. To avoid cookie warnings, I refrained from using any analytics services. When there were pricing changes, I grandfathered in existing users. I don't send any marketing emails, and basically avoid doing anything that annoys me as a user when other companies do them to me.
My primary motivation was to try new things rather than to generate profit as soon as possible. I could afford to experiment like that because I had a reasonably well-paying day job relative to the cost of living in Latvia.
What went into building the initial product?
I based the project on Django because this was a framework I was already proficient in, and I did not want to waste time learning new tools. I wanted something useful up and running as soon as possible. It took me about one month working in my spare time from the first Git commit to launching the initial version.
It had the absolute minimum amount of features for it to be considered useful: user registration, a simple dashboard of the monitored systems, an API endpoint for receiving pings, and email alerts. Initially there were no paid plans, no multiple notification methods, no team access, no ability to organize things into projects.
Everything was running off a single $5/mo DigitalOcean droplet, but it also initially saw very little traffic so that was fine. Since the code was open source, I could take advantage of the "free for open source" plans with GitHub, Travis CI, and Coveralls. I pay it forward by offering the paid Healthchecks.io plan to open-source projects and nonprofits for free.
I made a deliberate decision to keep the technology stack as simple as possible, for as long as possible. As few as possible dependencies in "requirements.txt," traditional PostgreSQL database instead of some fancy distributed data store, no task queue or message broker, simple deployment procedure with as few abstraction layers as possible, and no dependencies on proprietary technologies to avoid vendor lock-in.
I might end up adding some or all of these things eventually, but I want to see how far I can take this simple setup of just a Django app and a PostgreSQL database at its core.
How have you attracted users and grown Healthchecks.io?
The main strategy has been to provide good service and let the word of mouth do the work. I'm happy to see the existing users recommending Healthchecks.io on Twitter, Reddit, forums, and elsewhere. This brings in direct traffic and helps with Google rankings. This effect gets stronger over time as the user base grows. For example, there are fairly regular "What do you use for cron monitoring?" questions on Reddit. Usually by the time I discover them, somebody has already commented with a link to Healthchecks.io or even given their testimonial.
Seeing recommendations and good feedback is also an incredibly good motivator to keep working on new features and polishing the existing ones.
When there is something substantial to share I write a blog article, cross-post to Medium, and submit it to Hacker News. I've had only one article get upvoted to the Hacker News front page. This was in our first year and brought in a good amount of early users. As a non-native English speaker, I usually pay somebody on Fiverr to proof-read my blog articles; I'm always surprised how many mistakes they find. Definitely worth the literal fiver.
One small thing I do is include a "Powered by" line in the footer of the open-source project. When somebody self-hosts a Healthchecks instance and does not customize the footer template, it shows up there. I don't think this makes much difference with Google rankings, but it spreads the awareness among people who use or stumble upon the hosted instance.
I also dabbled with Reddit, Google, and Twitter ads. Though I could see how many people clicked, I did not have any conversion tracking because I didn't want to add tracking pixels. The ad budgets were small, so it's hard to know how many people signed up and if anybody upgraded to a paid plan because of the ads. But it was interesting to experiment with different creatives and targeting options. I did like how I could target specific subreddits or followers of specific Twitter accounts.
What's your business model, and how have you grown your revenue?
Freemium and paid monthly or annual subscriptions. The "Hobbyist" plan is free, and can be used to monitor up to 20 services. The "Business" plan is $20/mo and can monitor up to 100 services and supports more team members. I quite often see cases where a user starts with a free account, their usage grows slowly, and then they finally convert to a paid subscription maybe two years later when they have finally hit the limits of the free plan.
Healthchecks.io uses Braintree to process payments and recurring subscriptions and integrates with it directly. As far as I know, Braintree does not generate a PDF invoice so I implemented that on my side. I pulled together a script to generate VAT reports for accounting. Recently I updated the billing code to support 3D secure. If I were starting today, I would consider using an additional service on top of the payment gateway to save me some of that work.
Today Healthchecks.io has more than 7,000 active user accounts, and 150 users are on paid plans. Current MRR is $2,200. It is not yet enough for me to go full time, but the monthly revenue is steadily creeping up. I expect that Healthchecks.io will become my primary source of income and my primary occupation sooner or later.
I see this more as a marathon, not a sprint.
What are your goals for the future?
I don't have ambitious goals; the plan is basically to carry on with small incremental improvements. A major milestone will be when I go full time with this project. After that, a partner or first hire to reduce the bus factor. Currently it's just me running everything. Since I cannot be at my PC 24/7, it would be good to have other people being able to jump in and fix problems.
If you had to start over, what would you do differently?
When I started out, I didn't appreciate how important being reliable as a monitoring service is. If I had decided to work on something that is less sensitive to even tiny outages, my job would have been a lot easier. I enjoy the challenge but I wish I was aware of this aspect when I started out.
Also, launching a service means keeping it running for potentially the long term. When I launched the MVP, I didn't think about how long the "long term" might be. I think this really first struck me when one client asked if they could have a three-year billing period instead of just annual. It's all good, but it is something I didn't think about enough when I started.
Have you found anything particularly helpful or advantageous?
Being bootstrapped and relatively stable financially means that there is no pressure to generate profit fast. I can make decisions that are good for users but not necessarily good for short-term profit. I can take a break from new feature development, or I can spend time on a small detail that only a few people will notice.
What's your advice for indie hackers who are just starting out?
If you enumerate every tool and skill that goes into building a complete project, the list would be pretty overwhelming.
I guess the best advice here is to just start somewhere; start with something simple and don't be afraid to learn new tools and skills, even the ones you think you may never use. Sooner or later they will come in handy.
Where can we go to learn more?
- Website: https://healthchecks.io
- Blog: https://blog.healthchecks.io
- Development @ GitHub: https://github.com/healthchecks/healthchecks
—, Founder of Healthchecks.io
Want to build your own business like Healthchecks.io?
You should join the Indie Hackers community! 🤗
We're a few thousand founders helping each other build profitable businesses and side projects. Come share what you're working on and get feedback from your peers.
Not ready to get started on your product yet? No problem. The community is a great place to meet people, learn, and get your feet wet. Feel free to just browse!
—, Indie Hackers founder