openstatus.dev
Openstatus
www.openstatus.dev
hotfix: blog typo
+2
-2
+2
-2
apps/web/src/content/posts/reflecting-1-year-building-openstatus.mdx
+2
-2
apps/web/src/content/posts/reflecting-1-year-building-openstatus.mdx
···
48
48
1. **Serverless monitoring**: Given that most of our users were Vercel customers, we considered specializing in this area.
49
49
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.
50
50
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.
51
-
4. **Real User Monitoring (RUM)**: We implemented this feature, but after discussions, we recognized the need to focus in our core strength: synthetic monitoring.
51
+
4. **Real User Monitoring (RUM)**: We implemented this feature, but after discussions, we recognized the need to focus on our core strength: synthetic monitoring.
52
52
53
53
Ultimately, these explorations helped us refine our focus and understand our unique value proposition in the market.
54
54
···
78
78
79
79
### Leveraging Cutting-Edge Technology
80
80
81
-
By utilizing the latest tech, we caught the attention of theirs developers, who shared our work on twitter bring us more visibility.
81
+
By utilizing the latest tech, we caught the attention of theirs developers, who shared our work on twitter bringing us more visibility.
82
82
83
83
We were early adopters of Turso, Next.js server actions, Bun, and Hono.
84
84