Folks, in your launch posts remember to describe what you're launching and what it's for. Ideally in the opening paragraph.

- Intro: Explains problem but not what is Neki or what it's for.

- Why Neki: Explains alternatives and why they suck but not what is Neki or what it's for.

- How does Neki work: Describes the technical components but not what is Neki or what it's for.

- What you get beyond sharding: Explains how to run/deploy but not what is Neki or what it's for.

- What is a platform preview + Try Neki today: 140 words on the definition of "preview" and links to get started... but not what is Neki or what it's for.

Edit: The landing page has 100x more useful information up front -> https://neki.dev/

A C2 level diagram included in the blog post would be helpful. What are the drawbacks to using Neki aside from the obvious (new software has bugs)?

Man, I was deep into this blog post before I was able to answer the question "what is Neki?".

Will this be open source at some point?

Site design is tight. I like it.