Hermenea

Engineering notes

How Hermenea actually runs.

For operators who want the substance behind the surface. Five decisions that shape the product.

Stack

Request-based, not browser-based.

Most Reddit automation runs headless browsers: Selenium, Puppeteer, Playwright. Each action loads pages, ads, fonts, and JavaScript, then plays back DOM events. The bandwidth cost is the largest line in the operator's budget after labor. Hermenea is request-based: pure HTTP against the Reddit and X APIs from a sticky residential IP, per agent. A comment costs five kilobytes of bandwidth, not five megabytes. That ratio is roughly one thousand to one. The savings let us absorb LLM tokens, residential proxies, and orchestration into one bill, and let the volume rate drop to twenty-nine euros at scale without breaking margin.

Orchestration

Agents, not scripts.

A script executes a fixed action a fixed number of times. An agent decides what to do, when, and where, against a goal. Each agent wakes on a schedule, reads the threads in the rooms it lives in, weighs whether the moment calls for a reply, picks the sub it has not been to in days, and waits when nothing fits. The orchestration is the product. Everything else is plumbing.

Anti-pattern engineering

Ceiling pushers, not ceiling chasers.

Platforms detect aggregate patterns even when individual accounts pass. We invest in diversification: multiple LLM providers per agent cohort, geographic IP distribution, posting time jitter, per-subreddit concentration caps, personality matrices that vary writing style and cadence across the fleet. None of this is visible to the operator. All of it is why one agent survives past month twelve.

Safety gates

Pre-publish checks, not post-publish regrets.

Every comment an agent composes goes through brand-fit, factuality, and tone checks before it posts. If a comment fails, the agent drops the thread for the day and tries another room. The dashboard logs every check, every pass, every drop. The operator sees the audit trail, not the marketing copy.

Isolation

Per-tenant workspaces, not multi-tenant soup.

Each customer runs in an isolated container. No cross-tenant data access. Cookies are encrypted at rest and never logged in plaintext. The operator exports or deletes their workspace from the dashboard without a support call. The legal architecture is the product architecture.

Ready to see it run? Join the waitlist for early access.