Embed
A team of two FDEs and one platform engineer joins your unit on site. Week one is observation: how decisions get made today, where the data lives, what's broken.
Services · 03
FDE-led delivery
Forward Deployed Engineering. Swiss-cleared. On site.
Ithildin does not ship software and walk away. We embed our engineers directly inside your operations — sitting beside your analysts, commanders, and operators — until the platform is producing real decisions in production. Every Ithildin FDE holds, or is in process for, the Personensicherheitsprüfung (PSP) at the level your engagement requires.
04 — Engagement model
Three steps. Embed, integrate, expand.
The arc of an Ithildin engagement is short on first prototype, long on production. We arrive small. We hand off when you are ready.
Integrate
We build the ontology against your real data, in your environment, using your classification framework. Working prototype in five days under the Ithildin Engagement model.
Expand
Successful prototypes become production workflows, then enterprise rollouts. We hand off to a customer Center of Excellence when you are ready to operate independently.
05 — The Ithildin Engagement
Five days. Fixed scope. Fixed price.
A Swiss-priced, Swiss-staffed bootcamp that ends Friday with a working application your operators can use the next week.
Engagement · IE-01
The Ithildin Engagement
Duration 5 working days
Team 2 PSP-cleared FDEs, on site
Price Fixed · Swiss-priced
Location Customer site
Outcome Working application
Risk No deliverable, no payment
We arrive Monday with the platform on a hardened laptop, integrate against a sample of your real data, and leave Friday with a working application your operators can use the next week. If it does not deliver, you do not pay.
Mon · Day 1
Arrive on site. Observe operations. Define the single decision the prototype will support.
Tue · Day 2
Connect to the data sources. Map objects and actions to the ontology. No copies leave site.
Wed · Day 3
Build the application. Functions, views, write-back. Operator test on real (non-classified) data.
Thu · Day 4
Iterate with operators. Tighten access, classification, audit. Train the first user cohort.
Fri · Day 5
Hand-off. Documented prototype, deployment runbook, options for production rollout.
06 — PSP-cleared, Swiss-citizen engineers
The team that walks into the bunker is the team that built the platform.
Personensicherheitsprüfung (PSP) screening at the level the engagement requires. No subcontracting outside Switzerland. No offshore reach-back.
PSP · INTERN
Routine
Standard engagements with Swiss federal and cantonal authorities, critical infrastructure, regulated industry.
PSP · VERTRAULICH
Sensitive
Engagements involving non-public operational data, sensitive procurement, or regulated financial infrastructure.
PSP · GEHEIM
Classified
Engagements with the Swiss Armed Forces, NDB, and partner agencies on classified networks. Air-gap deployments.
One engagement. One working prototype. One Friday.
Briefings are by introduction. Reach out via Armasuisse, an existing advisor, or directly.