Assess · train · stay alongside jacob.poot@itkaro.com
NLEN

The tools · for engineers

How it is built.

Built myself: the learning portal, the assessment tool, the Dutch lesson portal, the investment dashboard, the cockpit, the customer portal and this site.

You hire me, and this is what I bring. I built the learning portal your people work in myself, so a tailored course gets the same tests and the same progress tracking as the existing one. Below is what runs, what it looks like and how it fits together. It is the same way of working that is in the lessons.

Back to what you get as the client 

Book an intro call View all training

The state of it

What is running right now.

11
applications live
2,400+
automated tests
9
applications where signing in with a passkey is possible
6
with their own deployment chain

All built myself, with AI as a tool. That way I have done version control, testing and deploying in production six to eleven times.

From idea to running it

From an idea to something that keeps running.

This is the question decision-makers ask most: so how does that work, building with AI? Like this. Six steps, and none of them is skipped. The last step is: who runs it afterwards? Press the button to see it with an example.

IdeaYou say what you are missing.example: the button turns orange Building with AIBuilt myself, tests underneath. TestingTests first, then deploy. RecordingEvery version kept. Trial, then liveFirst trial, then real, in Amsterdam.Send Running itWho owns it, and what if it breaks.

This is how I work on the six applications with their own deployment chain: the script runs the tests first and only then deploys. Across all applications together there are over 2,400 automated tests.

Secure by default

Four things, and where the limit is.

Signing in with a passkey where possible

Nine applications allow signing in with a passkey: your fingerprint or face. The learning portal asks for a password; you can add a passkey yourself.

Secrets outside the code

Keys and passwords are never in the code, only on the server itself.

A security policy with every page

With every page this site sends a policy that makes the browser refuse scripts from another origin. It is one layer, not a guarantee.

A snapshot every day

The hosting provider takes a daily snapshot of the disk holding the database.

How it is put together

How one of these applications is put together.

The same pattern every time, and that is deliberate: one way that is well understood works best. This is also the shape explained in the lesson.

Browserworks withoutJavaScript too https ONE SERVER, ASLEEP WHEN NOBODY IS LOOKING Proxyhttps, headers,static files Applicationpages built onthe server Databaseon its owndisk Log in with a passkey where possible Snapshot every day
A simple setup. One database on one disk, so there are never two versions of the truth.

What is running

Seven of the eleven applications, four with a screen.

Each of these applications is built the same way as above. For four of them you see real screens here, with made-up data in them. What is missing from this page is private or belongs to a client.

The learning portal

Courses with real AI exercises, tests and progress per participant. This is where your people work.

The learning portallearning.itkaro.com1 of 3
The free trial lesson in the learning portal: one lesson from the basic course, open without an account.
  1. The trial lesson is the first lesson of the course, as a participant sees it. No account needed.
  2. The size of the whole course: lessons, exercises with a real AI model, and tests.
A test result: the mark and, per question, what was right and why.
  1. The mark is there at once. The server does the marking; it also works without JavaScript.
  2. Right or wrong per question, with the given answer and the explanation. So a test teaches something too.
The test results of a group as the teacher sees them: marks per participant and who has not started.
  1. The teacher sees the marks of the whole group. A participant only sees their own, an employer none.
  2. The best mark per participant. Below it: who has not started, and per question how many got it right.
Real screen, made-up data. Captured October 2026.
For engineers

FastAPI and SQLite, pages rendered on the server. Everything works without JavaScript. 736 tests.

Take the free trial lesson 

The assessment tool

Upload documents, assess the evidence per item, and a report the board can read. This screen is the supplier governance scan: the same set-up and the same screens, with a different questionnaire. The security version runs on client data and is therefore not shown here.

The assessment toolscreen: the supplier governance scan1 of 3
The dashboard of an assessment: the overall score and the score per chapter, with coverage.
  1. The overall score, with how many of the 49 items have evidence and how certain that is.
  2. The score per chapter, from 1 to 5. A dash means: not assessed, so no score.
The evidence review: per quote the source, the role and the buttons to accept or delete.
  1. Whatever does not fit the framework is kept apart and counts in no score.
  2. Every piece of evidence is a literal quote, with the role of who said it. It only counts once a person accepts it.
The risk register: a proposed risk with impact, root cause and the finding it rests on.
  1. A risk is proposed and waits for a decision: accept, put on hold or reject.
  2. Every risk points back to the finding and the item it rests on.
Real screen, made-up data. Captured October 2026.
For engineers

Next.js, TypeScript and Postgres. Data is stored encrypted under a master password; sign-in is with a passkey. The screens are in English, the report is in Dutch. 520 tests.

Discuss a scan 

The Dutch lesson portal

A student tracking system for a single teacher. Each lesson is made from that one student's file: profession, goal, level per skill, and what went wrong in the previous lesson. The homework is attached to the lesson; the student does it in the portal, and the result is the input for the next lesson. A learning plan per student keeps itself up to date from the lessons, the homework and the measurements; I only add the milestones.

In October 2026 eight students work in it, and since late August twenty-four lessons have been given through the portal. The picture shows an example student.

The Dutch lesson portalfor my Dutch lessons1 of 3
The example student's own page: the lessons, with what is already done.
  1. Alex is the example student and does not exist. A real student sees their own lessons here.
  2. Every lesson stays available to read back, with its state: done or still open.
A slide from the example lesson: matching expressions to their meaning, with a button to check.
  1. An exercise that checks itself: match the expression to what it means.
  2. The lesson is made for this student: the words come from the job in the file.
The same lesson for the teacher, with the teacher panel open: counters per kind of mistake and a notes field.
  1. The teacher panel next to the slide. The student does not see it, not even when I share my screen in lesson mode.
  2. During the lesson I count mistakes by kind. With the notes below, that becomes the material for the next lesson.
Real screen, made-up data. Captured October 2026.
For engineers

FastAPI and SQLite. A lesson is a YAML file and is baked to HTML twice: once for the teacher, once for the student. 884 tests.

The investment dashboard

For founders: what you want to see about your own money as an entrepreneur. What there is, what it is in and what it did. The amounts are sample data from the app itself.

The investment dashboardfor founders1 of 3
The overview: total value, money put in, the result and the trend over a year.
  1. The total value of everything together: funds, crypto, gold, savings and a house.
  2. The result per period, after subtracting what was deposited. A deposit does not count as profit.
  3. Money put in and result are shown separately, so you see what the money itself did.
The target allocation: per asset class the target, the current share and what to buy.
  1. The target per asset class, as a percentage and in euros.
  2. The current share next to it. The bar in the next column shows how far off it is.
  3. What to buy to get back to the target.
The history: value per day over a year, with money put in as a second line.
  1. The value per day, calculated back from the transactions and the price on that day.
  2. The return is money-weighted: money added later counts for a shorter time.
Real screen, made-up data. Captured October 2026.
For engineers

FastAPI and SQLite; the charts are SVG from the server. No price was fetched for the capture: the prices are those from the sample transactions. 1,001 tests.

Book an intro call 

Also live

The cockpit

The company's numbers on one screen: revenue, hours, pipeline. Updated every morning.

itkaro internal

This site

Fast, without cookies, with a small program behind it for the contact form and the measurement.

itkaro.com

The customer portal

One sign-in with a passkey, and behind it the apps the customer is entitled to.

customer.itkaro.com

Why this is here

What it means for a participant.

From my own work

I have done version control, testing and deploying in production six to eleven times. That experience comes with me when a team starts building for itself.

It is from this week

I still build every week. When the tools change, the lesson changes with them.

It can be done

One person, with AI as a tool. That is the position most participants are in too.

What is not shown here

And why not.

The screens above are real. I started the applications on my laptop and a script took the pictures. The data in them is made up, and nothing has been blurred or painted over: what you are not allowed to see was never in there.

Private applications and anything belonging to a client are left out on purpose, in the diagrams too: those show the pattern. I do not use client names unless the client has said yes to that.

Contact

Learn this too?

View all training Book an intro call

The Fixed knowledge day: a fixed day a week alongside your IT team