Phare
Run brilliant websites
Over the years, Phare.io’s app (signed-in) experience has been gradually modernized, but the public-facing landing pages were starting to feel out of sync.
So I took a focused week to give the whole site a fresh coat of paint. Now, Phare is rocking a fully refreshed design across the board, new pages, sharper feature descriptions, and a spicier, more confident tone of voice.
Feels good 😎
Phare has seen significant growth and development over the months. I've reworked the monitoring infrastructure that now runs on 100% European-owned hardware, and introduced several new features, with status pages being the standout addition.
📄 Status Pages
Display all your monitors on a fully customizable status page. Use your own domain name and branding, write incident post-mortems, and let users subscribe to incident notifications via RSS/Atom feeds. This is the fastest available status page, powered by European cloud infrastructure and renewable energy.
💸 90% more affordable
Buying a Phare subscription is now cheaper than ever, starting at only €5 per months, making it a competitive alternative to self-hosted solutions. No tiered plans, no feature gating, only pay for what you use.
🌍 New monitoring regions
All uptime monitoring regions run on an upgraded infrastructure. Expect lower latency, improved efficiency, and even more reliable insights, now also available in Australia, Thailand, and Brazil.
🟢 Embed badges
Show your status on your landing page, GitHub repository, or wherever you like with sleek customizable embed badges.
🤖 API
The new API, currently in beta, allows you to interact programmatically with the Phare platform. Create custom uptime monitoring flows or explore endless possibilities with your own code.
⚙️ New integrations
Use outgoing webhooks to seamlessly connect Phare to third-party tools, or build your own integrations for enhanced functionality.
Pushover and Telegram can now be used to receive alert notifications, on top of the previously existing Slack, Discord, and emails channels.
🎁 Phare for good
A give-back program has been created, offering an extended free plan to nonprofit organizations and open-source projects and support their mission.
✨✨✨
Big improvements are still ahead, let's keep the light on!
Exciting news, Phare.io crossed 200 active users! 🎉
It’s an incredible journey to build a SaaS and see it slowly grow. This milestone means a lot to me, and it’s just the beginning!
A big thanks to all of you for the support, feedback, and love received during the last two years.
Today after the public launch on Product Hunt, Phare acquired its first paying customer 🎉
This will probably cost me more in taxes and accounting than what I'll earn, but it's a great feeling to have someone willing to pay for something you built.
It's also a great motivation to keep working on Phare and make it better and profitable.
-
1
congratS!
Decided Phare was good enough for a public launch and posted it on Product Hunt. Got a few new users and some great feedback to improve the product!
I'm now working on keeping the momentum going to attract free users and customers, while improving the platform to realize my long term vision.
After 6 months of hard work on the platform, I finally completed the Phare MVP. The first tool is an uptime monitoring solution, with email and Slack integrations for alerting, and a few useful configurations that should make it good enough for 90% of projects.
The next few weeks will be crucial to make sure everything is working as expected and complete the incident management features before a public beta opening in a month or two.
Every year, as part of my day job, I code between two to four projects, from idea to production. For each one of these projects we need a lot of external tools, for monitoring uptime, catching exceptions, capturing logs, monitoring security, implementing analytics, changelog, support, and more...
There are, of course, a ton of SAAS or open-source tools that do a great job of solving each of these things, but setting up that many services is cumbersome to say the least, each with its own configuration, setup and billing process.
This is why I'm building Phare, a minimalistic monitoring toolkit that does it all.
Comment