
Simas Ražinskas
Founder & Engineer
Foresttasks is built by one engineer who needed it to exist — not a hobby project, the control plane behind real, shipping work.
I'm Simas Ražinskas — a full-stack software engineer who takes systems from a first sketch all the way to production, and then keeps them running there. Foresttasks isn't a venture-backed startup or a weekend experiment; it's the tool I built because I needed it to exist for my own work.
For the past year I've run what I call an agent-operated engineering practice: AI coding agents do most of the actual building, while I design the architecture, define the guardrails, and review and deploy. The interesting part was never the prompting — it was building codebases and processes so mechanically sound that delegated work simply can't quietly go wrong.
That belief is the whole thesis behind Foresttasks. If agents are going to do real work, the system around them has to make “done” mean something: atomic claims so two agents never collide, an append-only provenance spine so every decision is traceable, and verification gates that check acceptance criteria before anything closes. You trust the result because you can replay exactly how it got there — on a deliberately conventional, self-hosted stack I run myself, on infrastructure in the EU, so when something breaks it's mine to understand.
Foresttasks runs exactly that way: multi-tenant, agent-first, harness-agnostic — Claude Code, Codex, Cursor, or anything that speaks MCP or REST plugs into the same queue — and dogfooded end to end. The work that builds Foresttasks is tracked, claimed, and verified on Foresttasks itself. It isn't a side project; it's the control plane for how I actually ship software — and now you can run your agents on it too.
The practice, turned into a product.
Foresttasks is the queue, the provenance, and the verification gates I rely on to ship with agents every day — now ready for yours.