Anton Taranovskyi Switzerland · --:-- ·

I'm Anton, a hands-on systems builder, surfing the frontier of IT for 20 years. I help businesses make things happen: from root cause to a system that actually works.

now focused on

The Process Execution Layer: deterministic, auditable, under your control.

What I'm crafting

Companies now have an app for everything and still run half the business by hand. Orchestrating all of it is hard, and the small gaps between tools are the expensive part: they look like nothing until you close one.

What I want the execution layer to get right:

  • full control of where it runs, on your own infrastructure rather than someone else's
  • no metering to think about: nobody should skip an automation because of what each run costs
  • observability at the system level, so keeping an eye on it isn't a daily job
  • an AI process builder, so starting doesn't mean learning every system's quirks first
  • extendable at that same level, so a task never turns into a dead end
  • one place to orchestrate all of it, not a tab per tool
  • attention on the business need, not on the tooling

Most of it only shows under load, which is easier to watch than to describe:

arriving 0.0/s waiting 0
done 0 failed 0 lost 0
fig. 1 · this is ops by hand. flow8 is the alternative.

An AI model helps build the process and reads the parts where rules run out. It doesn't run them. Deterministic first, AI second: predictable results are the ones you can trust and build on.

discover

First in the queue

Shared team knowledgedetails soon

What the team knows usually sits in inboxes, chats and a few people's heads. Here it goes to one place the processes can read from directly, so context arrives with the work instead of someone going to find it.

Company mail intake and processingdetails soon

Everything arriving by mail gets read, classified and routed, then the usual steps run (extract, file, notify, whatever the case needs). Not a smarter inbox, more like the inbox stops being a queue someone works through by hand.

Voice agent process backbonedetails soon

Voice agents handle the conversation well enough; the actual work still happens after the call. This is the part behind it, so the agent hands off and the rest runs with normal rules, logging and access control.

Waiting on input (that's you)

If any of this overlaps with what you're building or running, I'd like to hear about it. Always open to compare notes. The easiest way is to grab a slot for a short call, or find me on LinkedIn.

book a time to talk