Lukasz Blania

What I actually do

I am a solo founder. Lumi Zone is my company, registered in Katowice, Poland, and PostSider is the product I build and run. That means I write the code, run the database, answer support, write this site and publish the posts you are reading. There is no editorial department, no ghostwriter and no outsourced content agency behind these pages.

PostSider started because I wanted a scheduler that an AI agent could drive without browser automation. The result is one publishing layer with two front doors: a calendar for people and an MCP server, REST API and SDK for agents and scripts. I built the agent surface first because that was the part missing everywhere else.

Why the writing sounds like this

I test claims against the product before I publish them. When a page says a plan covers five channels, that number comes from the pricing page, not from a draft written months earlier. When a comparison quotes a competitor price, the page names the source URL and the date I read it. I ran a full audit in October 2026 that removed claims which had drifted from the product, including a tool count that was three releases out of date and a package described as unpublished when it was live.

I do not publish invented numbers, customer logos, testimonials I have not received, or case studies without a source. If a claim cannot be checked, it does not go on the page, even when the page would read better with it. That is why some of these pages say "not confirmed" in a table cell.

What PostSider does not do, in my own words

The product schedules and publishes. It does not read your DMs, it does not reply to comments, and it does not write your posts. The AI checks a caption against platform rules and can rewrite it; that is the whole of it. There is no free plan, no RSS auto-posting and no native mobile app. I built a publishing layer, not a social media suite, and the pages here say so even when it costs a sale.

Where the experience comes from

Before PostSider I spent years building and shipping software products, most recently as an engineer and product person in small teams where the same person writes the code and explains it. I also run PostSider's own social accounts through PostSider, including the release announcements, which is how I find the failures that end up in the troubleshooting guides.

If you want the rules I follow when I publish, they are on the editorial policy page. If you want to check a claim in a comparison, the comparison hub links every table with its source date. To report an error, email lukasz@postsider.com and you will get a reply from me, not a ticket system.