openstatus.dev
Openstatus
www.openstatus.dev
📝 blog (#1017)
* 📝 blog
* 📝 blog
authored by
Thibault Le Ouay
and committed by
GitHub
0a493afd
0fb72b91
+217
apps/web/public/assets/posts/reflecting-1-year-building-openstatus/first-year.png
apps/web/public/assets/posts/reflecting-1-year-building-openstatus/first-year.png
This is a binary file and will not be displayed.
apps/web/public/assets/posts/reflecting-1-year-building-openstatus/image.png
apps/web/public/assets/posts/reflecting-1-year-building-openstatus/image.png
This is a binary file and will not be displayed.
apps/web/public/assets/posts/reflecting-1-year-building-openstatus/twitter.png
apps/web/public/assets/posts/reflecting-1-year-building-openstatus/twitter.png
This is a binary file and will not be displayed.
apps/web/public/assets/posts/reflecting-1-year-building-openstatus/us.png
apps/web/public/assets/posts/reflecting-1-year-building-openstatus/us.png
This is a binary file and will not be displayed.
apps/web/public/assets/posts/reflecting-1-year-building-openstatus/users.png
apps/web/public/assets/posts/reflecting-1-year-building-openstatus/users.png
This is a binary file and will not be displayed.
+217
apps/web/src/content/posts/reflecting-1-year-building-openstatus.mdx
+217
apps/web/src/content/posts/reflecting-1-year-building-openstatus.mdx
···
1
+
---
2
+
title:
3
+
"Our Journey Building OpenStatus: From Idea to Reality"
4
+
description: Reflecting on our first year of building OpenStatus, an open source synthetic monitoring platform that has grown to more than 6,000 GitHub stars and 5,000 users.
5
+
author:
6
+
name: Thibault Le Ouay
7
+
url: https://bsky.app/profile/thibaultleouay.dev
8
+
publishedAt: 2024-09-26
9
+
image: /assets/posts/reflecting-1-year-building-openstatus/first-year.png
10
+
---
11
+
12
+
In one year, we've grown our open-source synthetic monitoring platform to more than 6,000 GitHub stars and 5,000 users. This article will reflect on our first year of building OpenStatus.
13
+
14
+
<Image
15
+
alt="Total users on OpenStatus"
16
+
src="/assets/posts/reflecting-1-year-building-openstatus/users.png"
17
+
width={650}
18
+
height={575}
19
+
/>
20
+
21
+
22
+
23
+
We've written about OpenStatus's journey before:
24
+
25
+
- [Celebrated 48 hours of OpenStatus](https://www.openstatus.dev/blog/the-first-48-hours?ref=blog-1year)
26
+
- [Our 2023 year in review](https://www.openstatus.dev/blog/2023-year-review?ref=blog-1year)
27
+
28
+
## The Beginning: A Twitter Connection 🤝
29
+
30
+
It all started with a simple connection on Twitter. As members of the same developer community, we exchanged a couple of messages over the past few months.
31
+
Our shared experiences and complementary skills led us to a decision: why not build something together?
32
+
33
+
<Image
34
+
alt="Twitter"
35
+
src="/assets/posts/reflecting-1-year-building-openstatus/twitter.png"
36
+
width={650}
37
+
height={575}
38
+
/>
39
+
40
+
41
+
42
+
### Our Initial Goals
43
+
44
+
1. Launch a viable product collaboratively
45
+
2. Create a sustainable business.
46
+
3. Build an open-source product
47
+
4. Focus on developer tools
48
+
49
+
## The Evolution of our Idea 💡
50
+
51
+
Our journey began with a simple concept: a beautiful status page built with cutting-edge technology. We would populate this page with our own monitoring checks.
52
+
53
+
This initial idea served as the seed from which our entire project would grow.
54
+
55
+
As we progressed, we talked to a lot of users, VC. We explored various directions, sometimes feeling a bit lost in the sea of possibilities:
56
+
57
+
1. **Serverless monitoring**: Given that most of our users were Vercel customers, we considered specializing in this area.
58
+
2. **Incident management**: Inspired by products like [incident.io](http://incident.io/), we contemplated starting with status pages and expanding into incident management. However, we realized this would target larger, Series B+ startups, involving longer sales processes and diverging from our core audience of small teams from bootstrapped businesses or Series A startups.
59
+
3. **AI-enhanced alerting systems**: We briefly considered focusing on our product's alerting capabilities and incorporating AI for smart alerts. In retrospect, this seemed more like an attempt to capitalize on the AI trend rather than a strategic decision.
60
+
4. **Real User Monitoring (RUM)**: We implemented this feature, but after discussions, we recognized the need to focus in our core strength: synthetic monitoring.
61
+
62
+
Ultimately, these explorations helped us refine our focus and understand our unique value proposition in the market.
63
+
64
+
**We want to build the best open-source synthetic monitoring platform.**
65
+
66
+
In today's market, you'll find either closed-source products like Checkly and Datadog, or open-source solutions with poor user experience (such as Prometheus Blackbox Exporter).
67
+
68
+
## Understanding our Market 🏇
69
+
70
+
Prior to launching OpenStatus, we had experience with tools like:
71
+
72
+
- Atlassian Statuspage
73
+
- BetterStack
74
+
- Datadog
75
+
76
+
However, we weren't power users of these platforms. Our understanding of the ecosystem was broad but not deeply ingrained. This experience taught us a valuable lesson:
77
+
78
+
**You don't need to be an expert in a field before starting. The key is to begin building—you'll learn along the way.**
79
+
80
+
## Our Marketing Strategy 📈
81
+
82
+
### Riding the OSS train
83
+
84
+
We started at the right time where lots of Open-Source Software companies like our friends at [papermark.io](http://papermark.io?ref=openstatus.dev), [uninbox.com](http://uninbox.com?ref=openstatus.dev) or [documenso.com](http://documenso.com?ref=openstatus.dev) flourished at the same time and made it into the oss-friends list by [formbricks.com](http://formbricks.com?ref=openstatus.dev).
85
+
86
+
**Sometimes, you have to be lucky! We were fortunate to be in the right place at the right time, gaining the visibility that helped set us apart.**
87
+
88
+
### Leveraging Cutting-Edge Technology
89
+
90
+
By utilizing the latest tech, we caught the attention of theirs developers, who shared our work on twitter bring us more visibility.
91
+
92
+
We were early adopters of Turso, Next.js server actions, Bun, and Hono.
93
+
94
+
Being early adopters meant we encountered some bugs, but we could also benefit from the hype surrounding other products.
95
+
96
+
### Open-Source as a Marketing Tool
97
+
98
+
We embraced open-source not just as a development philosophy but as a powerful marketing strategy.
99
+
100
+
We were multiple times in the github trending repository both global and for typescript.
101
+
102
+
To be in these lists you don’t only need to ship feature but you have to engage with your community on github.
103
+
104
+
### Content Creation
105
+
106
+
We lacked a formal SEO strategy, but some of our blog posts performed well:
107
+
108
+
- [Monitoring Serverless Providers](https://www.openstatus.dev/blog/monitoring-latency-cf-workers-fly-koyeb-raylway-render)
109
+
- [Migrating our backend from Vercel to Fly](https://www.openstatus.dev/blog/migration-backend-from-vercel-to-fly)
110
+
111
+
Our content approach was straightforward:
112
+
113
+
> Write articles we'd love to read ourselves and not targeting keyword.
114
+
115
+
### Organic Growth
116
+
117
+
Our status pages served as an excellent marketing tool. Each time a user published one on their website, it created a valuable backlink for us
118
+
119
+
### Tools and Components
120
+
121
+
Additionally, creating tools and components people love is a great way to draw attention and leverage SEO: [time.openstatus.dev](http://time.openstatus.dev) - a shadcn time picker drives 3k visitors per month organically. Same goal is with [data-table.openstatus.dev](http://data-table.openstatus.dev) - an extensive data-table for your realtime data.
122
+
123
+
> We want to show users we are here to build with and for you. And of course in the open.
124
+
125
+
## Our Initial Approach: YOLO 🤘
126
+
127
+
In our early days , we adopted what we call a "YOLO" mindset.
128
+
129
+
Our approach was characterized by:
130
+
131
+
1. **Rapid iteration**: We moved swiftly from one idea to another, exploring various possibilities without getting bogged down in extensive planning.
132
+
2. **Flexibility**: Being a small team of two without external constraints allowed us to pivot quickly and adapt to new insights or market demands.
133
+
3. **Learning through action**: Instead of extensive market research, we learned by doing, gaining valuable insights through direct experience.
134
+
135
+
While this approach was exciting and allowed for quick exploration, it also had its challenges:
136
+
137
+
- **Lack of structure**: Our development process was often messy and lacked clear direction.
138
+
- **Inconsistent focus**: We sometimes struggled to maintain sustained effort on a single initiative.
139
+
140
+
Perfect example would be the RUM idea: after having that idea, the time and the will we build the MVP of that feature. But what happens next is that you have an additional infrastructure to maintain and suddenly a new product to market to sell, next to synthetic monitoring.
141
+
142
+
While it was fun, we don’t want to spread out too much and want stay in one domain and improve and make our users happy in that one, especially for a small team like us.
143
+
144
+
This yolo chaotic approach was sustainable while we had a limited user base.
145
+
146
+
However, now that we've grown to more than 5,000 users, we recognize the need for a more structured and strategic approach to continue scaling effectively and meeting our users' needs.
147
+
148
+
> Our customers rely on us; we can’t be flaky anymore, even though it was okay when we launched.
149
+
150
+
### Project Management
151
+
152
+
We experimented with GitHub Projects for our workflow, aiming to make everything open-source—including our ideas and tickets. However, this approach didn't quite fit our needs and we couldn’t dump everything into it.
153
+
154
+
Now, we've re-initialized Linear and are documenting our upcoming features more thoroughly.
155
+
156
+
It's our platform for brainstorming and iterating on ideas.
157
+
158
+
## Personal Journeys 🧳
159
+
160
+
### Max
161
+
162
+
- Maintained a full-time job throughout 2023/2024 and still is at the time of writing
163
+
- Plans to transition to OpenStatus at the end of the year
164
+
165
+
> After working evenings and nights on OpenStatus for over a year, I had to make a personal decision to cut back on my 9-to-5 job. I've been neglecting other pillars in my life that I want to nurture again. While losing the income security, I'll free up mental space and open myself to new opportunities.
166
+
>
167
+
168
+
### Thibault
169
+
170
+
- Left full-time employment in late February 2024
171
+
- Welcomed a daughter in early March 2024
172
+
173
+
Despite working remotely for most of the OpenStatus history, we finally met in mid-August. Max visited me, and we spent two great days:
174
+
175
+
- Cooking together 🥘
176
+
- Enjoying craft beers 🍻
177
+
- Family time (with our partners and the lovely baby 👶)
178
+
179
+
<Image
180
+
alt="Us"
181
+
src="/assets/posts/reflecting-1-year-building-openstatus/us.png"
182
+
width={650}
183
+
height={575}
184
+
/>
185
+
186
+
187
+
188
+
This time reinforced our commitment to OpenStatus and our shared vision for its future. We didn't write a single line of code during that time—proving that you don't need to grind 24/7 to make progress.
189
+
190
+
## The future 🚀
191
+
192
+
We all know it: You have created a dedicated roadmap that you’re excited working on but finally you start building everything else. And that’s fine (at a certain degree). The most important thing is to build, to learn and enjoy it - so that the inner drive keeps moving. We have been doing a lot of stuff that came up in the moment and build it (SDD - Self Driven Development) that does include bug fixes, user requests, community support on a higher priority.
193
+
194
+
As we reflect on our journey, we're excited about the road ahead. So how does our roadmap looks like (and we already know that it will not fully reflect the future - it’s a helpful path that provides us a North Star):
195
+
196
+
- More checker types like TCP, UDP, ICMP,…
197
+
- Improve the Single Checker experience via dashboard UI, config file, better use cases,…
198
+
- Create an Alert Management Engine and improve the notification channels
199
+
- Overall solidify the source code structure via tests, code splitting and staging environment
200
+
- Being more integrated into your o11y stack
201
+
202
+
> If you have ideas, requests or wanna chat feel free to contact us via [ping@openstatus.dev](mailto:ping@openstatus.dev) or join our Discord channel [https://www.openstatus.dev/discord](https://openstatus.dev/discord)
203
+
>
204
+
205
+
OpenStatus has grown from a simple idea into a promising open-source project with a dedicated user base. We're committed to continuing our innovation, engaging with our community, and building tools that developers love.
206
+
207
+
Stay tuned for more updates as we continue to improve OpenStatus!
208
+
209
+
210
+
<Image
211
+
alt="To infinity and beyond"
212
+
src="/assets/posts/reflecting-1-year-building-openstatus/image.png"
213
+
width={650}
214
+
height={575}
215
+
/>
216
+
217
+
To infinity and beyond 🚀