Aleksander Ambros Silesia, Poland

Your data lives in five systems. The answer is in none of them.

I build B2B systems that put this in order and then run every day, unattended, without you in the loop. For eight years I was responsible for a process with no second attempt: a bad run meant losing the entire batch, not restarting it. The same rule applies to my code.

Describe your problem See the proof

I run one project at a time.

GET /api/v1/companies/events 200

{
  "status": "success",
  "data": {
    "events": [
      {
        "event_type": "COMPANY_NAME_CHANGED",
        "old_value":  "NORBUD Sp. z o.o.",
        "new_value":  "NORBUD Sp. z o.o. w likwidacji",
        "event_date": "2025-04-14",
        "severity":   "warning"
      },
      {
        "event_type": "COMPANY_CLOSED_DATE",
        "old_value":  null,
        "new_value":  "2026-02-28",
        "event_date": "2026-03-02",
        "severity":   "critical"
      }
    ]
  },
  "meta": {
    "total":        2,
    "per_page":     20,
    "current_page": 1,
    "last_page":    1,
    "fetched_at":   "2026-03-24T15:20:44+00:00"
  }
}

An example of a real response structure; the entity data is synthetic. You do not have to take my word for it, you can check it yourself.

// Let us start with you

If any of these sentences sounds familiar, this is a topic for me.

I do not do websites or online stores. I work on situations where the data and the processes have outgrown the tools you are using to hold them together.

“We have the data, but the comparison is problematic”

Three systems, two spreadsheets, and an export that someone manually edits. I build a layer that consolidates, cleans, and maintains consistency, working autonomously without your involvement.

“Someone has to click through this every month”

Repetitive work that eats days and always ends in a typo. I turn it into a process that runs in the background and speaks up only when something is genuinely wrong.

“Nobody knows what changed, or when”

The last column tells you how things are now, not how they got there. I build systems where a change is a record: it has a date, a context, and lets you go back to any given day.

“Our data would be useful to our clients”

You want to expose it to partners or sell access, but there is nothing to expose it with. I build the entire public layer: an API with documentation, tokens, rate limits and billing.

// Proof

I do not have to claim I can do this. I can show you.

entiway solves exactly this problem, only at the scale of an entire economy. Registry data on Polish companies changes constantly, but registries show you a state, they never tell you what actually happened. I built a system that detects those changes, classifies them and serves them over an API. I designed it, wrote it and maintain it alone: from the database schema through the processing pipeline to the documentation, billing and customer panel.

I am not asking you to take my word for it. Open the API documentation and look at the endpoint structure. Visit the public registry activity board. You do not have to sign up or sign anything. This is not a case study written for this page, it is a system that was running before you asked about it.

Visit entiway → API documentation

Before

NGK Ceramics Polska

line supervisor · 8 years

3: ceramic kilns
6: FANUC robots
5: people on the crew
1: process to own

Now

entiway

B2B system · since 2017

5M: business entities
150M: descriptive records
50: event types in the API
19: queued for release

same work, different material

// Where this came from

There was no startup and no funding round. Since 2017 I pulled a little data from the Polish statistical office every day and taught myself PHP, in whatever time the shift pattern left me. Years later it had turned into a system handling one hundred and fifty million records.

In parallel, for eight years I was a line supervisor at NGK Ceramics Polska: three ceramic kilns, six FANUC industrial robots, a crew of five and the whole production process on my shoulders. Once a load went into the kiln nobody could correct anything any more, it came out either good or scrapped. I was the link between the office and the shop floor: translating one side’s intent into the other side’s execution, and answering for the result.

That is why a conversation with me does not start with technology. It starts with what actually happens at your company.

// Honestly

I have not yet had a client I built something like this for, and I am not going to pretend otherwise.

What I did have was eleven months I could pour into ten unfinished projects for other people, or into one I would carry all the way through. I chose the second. entiway is proof not because someone paid for it, but because nobody made me build it, and it is finished, maintained and running in production anyway.

// What it looks like in practice

One person doing the work, nobody in between.

01
You talk to the person writing the code

There is no account manager and no “let me take that back to the team”. You get an answer to a technical question straight away, not after two days of internal routing.
02
Process first, technology second

We start with what actually happens in your company: what the events are, where the boundaries sit, what breaks. The choice of tools follows from that conversation, it is not the starting point.
03
You get a working system

Not a presentation, and not a prototype for somebody else to finish. The result is something you can deploy and use.
04
It has to survive without me

Clear structure and documentation are part of the project, not a paid extra. Making a client dependent on me is a defect, not a business model.

I would rather say up front when I am not the right person.

Good fit

You have data and processes, not just a need for a website.
You need something that runs every day without supervision.
You want one person to talk to instead of an agency with three layers.
You care that somebody understands your process before writing code.

Poor fit

You need a brochure site or a store on an off-the-shelf engine.
The project has to start tomorrow and be done within a week.
You are looking for the cheapest hourly rate.
You expect a team of five from Monday.

The projects I take on are measured in months of work, not days. I run one at a time, so you don't have to queue with several others.

Three questions you are already asking yourself.

How do I know you will deliver, when you have no client references?: You do not have my word for it, you have a working system. entiway handles one hundred and fifty million records and paying users, and I designed it, wrote it and maintain it alone. Before that I spent eight years responsible for keeping a production line running, where downtime cost days. Those are the two proofs I have, and both can be checked without asking my opinion.
What if the project turns out to be bigger than one person?: I will tell you straight as soon as I see it, ideally while we are setting the scope, not halfway through the work. I would rather narrow the scope to what I can genuinely deliver, or hand part of it to someone you choose, than drag a project that is beyond me and realise it three months too late.
What happens after launch, am I left alone with the code?: You are left with code, documentation and a structure you can read without my help. That is part of the job, not a paid extra. If you want me to keep maintaining the system, we agree that separately. If you do not, or you would rather use someone else, nothing stops you, I design it that way from the start.

// Contact

Tell me what is jamming. I answer personally.

I do not need a specification or a finished brief. Describe your process and the point where it breaks, I will pull the rest out with questions.

What happens after you send it

I reply within a day and tell you straight whether this is something I can do.
A short call about your process, usually an hour. Mostly I ask questions.
You get the scope, the stages and a quote in writing. Only then do you decide.

Prefer plain email? [email protected]

Your email

What is jamming