Engineering blog
No blog yet. There will be one, and it will be founder-written for the first year — release notes, technical deep-dives on how the product works, and our own post-mortems. Never SEO-farm content; every post has a named author and a real argument to make.
What we plan to post, and how often.
Quality over volume. Steady-state cadence is roughly 2–4 posts per month once we're up and running.
Per release
Release notes
Short, factual notes on what shipped in each release. Linked to the changelog. Automatable by V2.
~1 per month
Technical deep-dives
How we built it — release attribution, the Auto-SRE triage pipeline, change-timeline correlation, how the AI triage prompts actually work.
Whenever they happen
Our own postmortems
Every Sev-1 / Sev-2 incident on Greenslope infrastructure gets a public post-mortem. Dogfooding we'd rather do than avoid.
With each major feature
Product showcases
New feature launches, written to be genuinely useful if you're considering the feature — not marketing gloss.
~1 per month, once customers exist
Customer success stories
Concrete incident / onboarding / scale stories from customers who are happy to be named. No testimonial fluff.
~1 per quarter
SRE thought leadership
Long-form on Auto-SRE, release-attribution research, SRE practice for small teams. When we have something to say.
Looking for something now?
While the blog is empty, the changelog is the most-current thing we publish. The documentation explains how the product works, and the product pages cite the job-to-be-done each surface serves.