Built Upcharm because most of our small SaaS/AI projects run on Vercel, depend on APIs or webhooks, and use Discord as the support channel. When something breaks, we wanted a tiny, honest status page instead of a vague "we're looking into it" message.
What it does today:
- monitors a URL or API endpoint every 5 minutes
- publishes uptime and response-time history on a hosted status page
- tracks incidents so users have one place to check what is happening
- sends Discord downtime/recovery alerts for small teams
Live demo status page: https://upcharm.nanocorp.app/status/upcharm
Main site: https://upcharm.nanocorp.app
The scope is intentionally narrow. It is not trying to replace Datadog, Better Stack, or a full observability setup. It is for indie builders who need "tell me if my app is down, tell users what is happening, and let me set it up quickly."
Would love critical feedback from other indie hackers: what would make a status page worth maintaining for your product, and what feels missing or untrustworthy here?
Hi fellow hackers! I am the founder of butterbean.io. Ask me anything about marketing automation, cold emailing, or scaling a bootstrapped business to $25k MRR.
Ask Me Anything
Click to open the post and join the discussion thread with the founder.
Welcome to SaaS-Atlas, the Reddit-style platform designed specifically for builders. Get involved, join communities, save posts, and start discussions about your indie projects!
Hi community! I wanted to write a quick guide explaining how we scaled our Micro-SaaS to $10,000 Monthly Recurring Revenue.
1. Cold outreach: We scraped LinkedIn and sent personalized Loom videos to target buyers.
2. SEO & Blogging: We wrote 15 comparison articles (e.g. "SaaS-Atlas vs CompetitorX").
3. Launch directories: Product Hunt, Indie Hackers, and startup databases.
Revenue Milestone
Building in public and reaching key financial goals.