Kastral

I took Kastral from a hard technical idea to a company people can understand, trust and visit.

01 / The mandatePositioning → product → production

Make sovereignty concrete. Show the boundary, the operator and the proof.

Kastral began with a serious proposition: Europe should be able to run AI without surrendering control. My job was to make that proposition legible. I wrote the positioning, mapped the platform, designed the identity and built the production website myself.

Not thisAnother AI wrapper

A feature sitting on somebody else’s operating boundary.

Not this eitherSovereignty as a slogan

Flags, clouds and promises without a system behind them.

The actual positionInfrastructure you can point to

Where it runs, who controls it and what evidence it leaves.

I ownedIdea + positioningProduct architectureBrand systemUX + interfaceCopy + narrativeFrontend + deployment

KASTRAL_CORE / SYSTEM MAPWESTEUROPE-01 OPERATIONAL

INBOUNDKCONTROLLED OUTPUT

02 / Translating the system

I did not make the complexity disappear.
I gave it somewhere to live.

Start with the boundary

Before talking about models, show where the system runs and who remains in control.

Let the hardware be hardware

The photography is dark because the machines are serious—not because every AI company needs a black website.

Do not dumb it down

The system is complicated. The job was to organise that complexity, not hide it behind three friendly feature cards.

Kastral hardware material study — Hardware study / Compute assembly

Kastral field operations — Field operations / Commissioning

What shippedA position.A system.A live website.One builder, end to end.

Next projectDisposable Azure environmentsEphemeral↗