Essays on privacy engineering, EU privacy regulation in practice, and the operational reality of building a small-team SaaS in public. This page is the standing index. Pre-launch, the index is empty; once we start publishing it lists the posts in reverse-chronological order.
Last reviewed 2026-05-17
LinkSilo is in active development, pre-launch. We have not yet published any blog posts publicly. The reason is straightforward: we would rather ship the product first and write about what we learn from operating it than write speculative posts about what we expect to learn. The pre-launch marketing surface — this page, the security page, the transparency page, the about page, the changelog — is the structural framework that the first wave of public-launch posts will arrive into.
Once the first post publishes, this section is replaced by a reverse-chronological listing. Until then: this page exists so the footer link in the marketing surface resolves to something honest about the current state rather than a 404.
The blog's editorial scope is shaped by the work the team actually does day-to-day rather than by an aspirational topic list. The four areas below are where we expect to have something specific to say. Posts that land outside these areas are possible but will be rare.
Concrete implementation choices on encryption, key management, role separation, and metadata minimization — the kind of detail that ends up footnoted on the security page rather than featured. When we make a non-obvious choice and write it up in code review, that write-up is often the seed of a post.
GDPR, the EU AI Act, the Digital Services Act, ePrivacy — applied to a specific small SaaS, not in the abstract. Where the regulation maps cleanly to a code path we describe the mapping; where it does not we describe the gap and how we handle it.
Three people, single VPS, EU jurisdiction, open source. The operational reality of running infrastructure at this scale without an SRE team — what works, what we deferred, what we learned the hard way. Honest accounting rather than highlight-reel.
Architecture choices, deprecations, post-incident reviews, the occasional product decision that needs explaining. The changelog tracks shipped changes; the blog provides the reasoning behind the ones worth explaining at length.
We deliberately do not run an email-signup form on this page at v1. The marketing surface already collects no visitor data; adding an email-capture widget here would diverge from that posture for the convenience of one notification channel. Once the blog has actual posts, an RSS feed will publish at /blog/feed.xml as the standard follow-along path. Until then, the channels below are the documented ways to check what's new.