Lyhnis is a workflow execution platform for teams whose automations have to be audited, durable and verifiable. We are a small team, building deliberately, talking to every customer.
Not marketing values - the product decisions we keep making, in writing. When something in Lyhnis feels deliberate, it is usually one of these.
Every action writes to the ledger because there is no code path that bypasses it - not because a compliance feature was added later. Insert-only, signed, actor-tagged.
See the audit ledger →Runs survive worker crashes, multi-day HITL waits and engine restarts. Per-turn dispatch means pause, resume and recovery share one primitive - and a 48-hour wait is the design, not a degraded mode.
See durability in the engine →HITL gates are optional and placed wherever the author chooses. The platform does not decide what is sensitive - you do. Destructive operations get step-up auth on top, every time.
See step-up auth in practice →Canvas, JSON and Python SDK are three views of one definition. Engineers are not patronised; ops teams are not locked out. Both refer to the same underlying object.
See all three views →Python source, JSON definitions and canvases all serialise cleanly. Diffs are reviewable, CI applies. Workflows are deployable artifacts - not opaque state in a vendor UI.
See the SDK reference →Every entry in the ledger signed with HMAC-SHA256 over a per-tenant key, chain integrity verifiable on export, security documentation on request. We do not ask you to trust us; we let you check.
See the security posture →Lyhnis is built by a small team based in [Skopje, Macedonia], with [engineering backgrounds]. We have watched what enterprise RPA became - slow, opaque, expensive - and what every "AI automation" platform skips: the durability, the audit trail, the human approvals. So we are building the other thing.
We talk to every customer. We ship every week. We write our own changelog. The team is intentionally small for now - we would rather be ten people who know every line of the codebase than fifty who do not.
If you want to know who is behind a feature you depend on, ask. If you want the roadmap for the next six months, ask that too.
No contact forms, no chatbots. Real addresses that real people read - use the one that matches your question.
[Skopje, Centar, 1000]
[Macedonia]
For evaluations, partnerships, or anything that warrants founder time, ask sales to route you. We respond.
Try the platform yourself, or talk to the team directly. We do not gate evaluations behind sales - but if it is a bigger conversation, we would rather have it.