Jonathan Hvid
9703d47407
Rework the supporter credits ("Backed by" / "Part of") into a
three-tier lockup — a small uppercase label over an upright Newsreader
serif name, with the parent body / issuing authority in a quieter
serif beneath — so the credits read in the deck's editorial voice
instead of as a foreign sans-serif caption. Applied consistently
across all three views:
- Entrance welcome screen: replaced three separately position:fixed
blocks (with hand-tuned top offsets) with one centred .welcome-credits
lockup; drops the brittle magic-number stacking.
- Timeline hero ("Fenja introduction"): left-aligned .support-credit
stack in place of the old .support / .support-bii lines.
- Mobile hero: matching .m-credit stack replacing .m-support / .m-backer.
Credits now read: Backed by Innofounder (Innovationsfonden); Part of
AI Lab (BioInnovation Institute); Part of The AI Regulatory Sandbox
(Datatilsynet & Digitaliseringsstyrelsen).
Also brings the mobile view to parity with the customer-facing desktop
deck: updated hero copy, platform-question framing, architecture layers,
Wiki deep-dive, deployment cards, and implementation roadmap; removes the
old "Join Project Bifrost" CTA + footer (mobile.js loses the join
handler, keeps the session check).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
626 lines
35 KiB
HTML
626 lines
35 KiB
HTML
<!DOCTYPE html>
|
|
<html lang="en">
|
|
<head>
|
|
<meta charset="utf-8" />
|
|
<meta name="viewport" content="width=device-width, initial-scale=1, viewport-fit=cover" />
|
|
<meta name="robots" content="noindex, nofollow" />
|
|
<meta name="theme-color" content="#faf6ee" />
|
|
<title>Fenja AI — Trusted & Sovereign AI</title>
|
|
<link rel="stylesheet" href="/fenja/colors_and_type.css" />
|
|
<link rel="stylesheet" href="/mobile/mobile.css" />
|
|
</head>
|
|
<body>
|
|
|
|
<header class="m-masthead">
|
|
<a class="m-logo" href="/" aria-label="Back to entrance">
|
|
<img src="/fenja/fenja-wordmark-black.svg" alt="Fenja" />
|
|
</a>
|
|
</header>
|
|
|
|
<main class="m-main">
|
|
|
|
<!-- ─── Timeline intro ─── -->
|
|
<section class="m-section m-intro">
|
|
<h1 class="m-title">When AI runs Europe, who runs the <em>AI?</em></h1>
|
|
<p class="m-body">
|
|
We’ve spent years building data and AI across Denmark and Europe, watching one dependency harden after another. AI is different. The United States has made that clear. China has made that clear. You cannot stand strong in this century on AI you do not control — and for the first time in a generation, Europe has both the reason and the moment to build its own. The window is closing faster than most realise. It is open now. It will not be open long.
|
|
</p>
|
|
<p class="m-body m-body--accent">
|
|
As AI moves into our hospitals, our courts, our defence, our schools — can we afford for the switch to sit in <em>Washington?</em>
|
|
</p>
|
|
</section>
|
|
|
|
<!-- ─── Timeline carousel (horizontal scroll-snap) ───
|
|
Twelve events become a single swipeable deck; each tile snaps
|
|
to the left edge so the user moves through one story at a
|
|
time instead of scrolling an endless vertical list. -->
|
|
<section class="m-section m-timeline" aria-label="Timeline of events">
|
|
<div class="m-timeline-intro">
|
|
<h2 class="m-section-head">The last 18 months, in twelve <em>moments.</em></h2>
|
|
<p class="m-swipe-hint" aria-hidden="true"><span>Swipe</span> →</p>
|
|
</div>
|
|
|
|
<div class="m-timeline-track" role="list">
|
|
|
|
<article class="m-event" data-accent="copper" role="listitem">
|
|
<div class="m-event-meta"><span class="m-event-kind">Editorial</span><span class="m-event-date">September 2024</span></div>
|
|
<h3 class="m-event-hed">Three American firms run 70% of Europe’s cloud — and almost all of its <em>AI.</em></h3>
|
|
<p class="m-event-body">Mario Draghi’s verdict to the European Parliament: only four of the world’s top fifty tech companies are European. “It is too late,” he writes, to challenge American cloud providers. Without radical reform, the EU faces “slow agony.”</p>
|
|
<div class="m-event-source">The Draghi Report · Brussels</div>
|
|
<div class="m-event-index"><span>01</span> / 12</div>
|
|
</article>
|
|
|
|
<article class="m-event" data-accent="copper" role="listitem">
|
|
<div class="m-event-meta"><span class="m-event-kind">Field Note</span><span class="m-event-date">December 2024</span></div>
|
|
<h3 class="m-event-hed">Denmark warns: digital society is now “extremely <em>vulnerable.</em>”</h3>
|
|
<p class="m-event-body">The expert group on tech giants reports: dependence on a handful of foreign suppliers is no longer a procurement question. It is a national security one. Minister Bodskov: “we need to fence in the tech giants.”</p>
|
|
<div class="m-event-source">Danish Expert Group · Copenhagen</div>
|
|
<div class="m-event-index"><span>02</span> / 12</div>
|
|
</article>
|
|
|
|
<article class="m-event" data-accent="crimson" role="listitem">
|
|
<div class="m-event-meta"><span class="m-event-kind">Rupture</span><span class="m-event-date">January 2025</span></div>
|
|
<h3 class="m-event-hed">Trump refuses to rule out military force against <em>Greenland.</em></h3>
|
|
<p class="m-event-body">Two weeks before inauguration, the president-elect threatens “very high tariffs” on Denmark. The shock in Copenhagen is total.</p>
|
|
<div class="m-event-source">Mar-a-Lago · Press Conference</div>
|
|
<div class="m-event-index"><span>03</span> / 12</div>
|
|
</article>
|
|
|
|
<article class="m-event" data-accent="crimson" role="listitem">
|
|
<div class="m-event-meta"><span class="m-event-kind">Rupture</span><span class="m-event-date">May 2025</span></div>
|
|
<h3 class="m-event-hed">Microsoft cuts off the ICC chief prosecutor’s <em>email.</em></h3>
|
|
<p class="m-event-body">A US tech company, complying with a US executive order, disables the digital life of an officer of an international tribunal in the Netherlands. The “kill switch” stops being theoretical.</p>
|
|
<div class="m-event-source">Associated Press · The Hague</div>
|
|
<div class="m-event-index"><span>04</span> / 12</div>
|
|
</article>
|
|
|
|
<article class="m-event" data-accent="copper" role="listitem">
|
|
<div class="m-event-meta"><span class="m-event-kind">Regulation</span><span class="m-event-date">June 2025</span></div>
|
|
<h3 class="m-event-hed">Microsoft admits under oath: it cannot guarantee European <em>sovereignty.</em></h3>
|
|
<p class="m-event-body">Even data on European soil, with European staff, encrypted with European keys — US authorities can compel disclosure under the CLOUD Act. The legal fiction collapses.</p>
|
|
<div class="m-event-source">French Senate Hearing · Paris</div>
|
|
<div class="m-event-index"><span>05</span> / 12</div>
|
|
</article>
|
|
|
|
<article class="m-event" data-accent="ochre" role="listitem">
|
|
<div class="m-event-meta"><span class="m-event-kind">Field Note</span><span class="m-event-date">June 2025</span></div>
|
|
<h3 class="m-event-hed">Copenhagen’s Microsoft bill jumps <em>72% in five years.</em></h3>
|
|
<p class="m-event-body">From 313 to 538 million Danish kroner. Copenhagen and Aarhus announce they will leave Microsoft entirely. The minister of emergency tells companies: “create exit plans for cloud services.”</p>
|
|
<div class="m-event-source">Copenhagen Municipality · Finance Report</div>
|
|
<div class="m-event-index"><span>06</span> / 12</div>
|
|
</article>
|
|
|
|
<article class="m-event" data-accent="copper" role="listitem">
|
|
<div class="m-event-meta"><span class="m-event-kind">Regulation</span><span class="m-event-date">Summer 2025</span></div>
|
|
<h3 class="m-event-hed">A Danish minister tells industry: prepare your exit plans for <em>cloud services.</em></h3>
|
|
<p class="m-event-body">Caroline Stage Olsen begins moving her ministry off Microsoft 365. The minister of emergency preparedness urges every Danish company to do the same. Continued dependence is now classified as a vulnerability.</p>
|
|
<div class="m-event-source">Danish Ministry of Digital Affairs</div>
|
|
<div class="m-event-index"><span>07</span> / 12</div>
|
|
</article>
|
|
|
|
<article class="m-event" data-accent="crimson" role="listitem">
|
|
<div class="m-event-meta"><span class="m-event-kind">Rupture</span><span class="m-event-date">August 2025</span></div>
|
|
<h3 class="m-event-hed">Trump threatens tariffs against any country with digital <em>regulations.</em></h3>
|
|
<p class="m-event-body">“American technology is not the world’s piggy bank.” The DSA, the DMA, the AI Act — all reframed as discriminatory trade barriers. Chip export restrictions are added to the list of consequences.</p>
|
|
<div class="m-event-source">Truth Social · Washington</div>
|
|
<div class="m-event-index"><span>08</span> / 12</div>
|
|
</article>
|
|
|
|
<article class="m-event" data-accent="crimson" role="listitem">
|
|
<div class="m-event-meta"><span class="m-event-kind">Rupture</span><span class="m-event-date">January 2026</span></div>
|
|
<h3 class="m-event-hed">Trump imposes tariffs on Denmark and seven <em>European nations.</em></h3>
|
|
<p class="m-event-body">10% in February. 25% from June — until Denmark cedes Greenland. Denmark, Norway, Sweden, Finland, France, Germany, Netherlands, UK. The post-war alliance, weaponised.</p>
|
|
<div class="m-event-source">Presidential Executive Order</div>
|
|
<div class="m-event-index"><span>09</span> / 12</div>
|
|
</article>
|
|
|
|
<article class="m-event" data-accent="crimson" role="listitem">
|
|
<div class="m-event-meta"><span class="m-event-kind">Rupture</span><span class="m-event-date">January 2026</span></div>
|
|
<h3 class="m-event-hed">Denmark names the United States as a national security <em>threat.</em></h3>
|
|
<p class="m-event-body">For the first time in history, the official Danish threat assessment lists the US alongside Russia and China. Defence committee chair Rasmus Jarlov tells Washington: “You are the threat. Not them.”</p>
|
|
<div class="m-event-source">Danish Defence Intelligence · FE</div>
|
|
<div class="m-event-index"><span>10</span> / 12</div>
|
|
</article>
|
|
|
|
<article class="m-event" data-accent="terracotta" role="listitem">
|
|
<div class="m-event-meta"><span class="m-event-kind">Product</span><span class="m-event-date">February 2026</span></div>
|
|
<h3 class="m-event-hed">The court that prosecutes war crimes can no longer use American <em>software.</em></h3>
|
|
<p class="m-event-body">The ICC migrates to OpenDesk — an open-source suite delivered by the German Centre for Digital Sovereignty. If a global tribunal cannot trust Microsoft, the implication for every other European institution is unavoidable.</p>
|
|
<div class="m-event-source">Handelsblatt · The Hague</div>
|
|
<div class="m-event-index"><span>11</span> / 12</div>
|
|
</article>
|
|
|
|
<article class="m-event" data-accent="copper" role="listitem">
|
|
<div class="m-event-meta"><span class="m-event-kind">Regulation</span><span class="m-event-date">Q1 2026</span></div>
|
|
<h3 class="m-event-hed">Europe drafts a sovereignty law as US firms still hold 70% of the <em>cloud.</em></h3>
|
|
<p class="m-event-body">Europe writes rules for infrastructure it does not own. US hyperscalers add €10 billion of European capacity every quarter — more than Gaia-X spent in a decade. The servers stay in Texas. The AI models stay in California. The law changes neither.</p>
|
|
<div class="m-event-source">European Commission · Brussels</div>
|
|
<div class="m-event-index"><span>12</span> / 12</div>
|
|
</article>
|
|
|
|
</div>
|
|
</section>
|
|
|
|
<!-- ─── Transition ─── -->
|
|
<section class="m-section m-transition">
|
|
<span class="m-rule-top" aria-hidden="true"></span>
|
|
<p class="m-transition-eyebrow">How Fenja AI <em>addresses</em> this</p>
|
|
<span class="m-rule-bottom" aria-hidden="true"></span>
|
|
</section>
|
|
|
|
<!-- ─── Hero ─── -->
|
|
<section class="m-section m-hero">
|
|
<div class="m-hero-mark" aria-hidden="true">
|
|
<img src="/fenja/fenja-wordmark-black.svg" alt="" />
|
|
</div>
|
|
<p class="m-eyebrow">For regulated environments</p>
|
|
<h2 class="m-hero-title">
|
|
Trusted & <em>Sovereign AI</em> built in Denmark, for <em>Europe.</em>
|
|
</h2>
|
|
<p class="m-hero-lede">
|
|
Fenja AI is both our company and our platform — one mission, one name. An entirely client-managed AI platform built in Denmark, so Danish and European organisations can take full control of their own AI.
|
|
</p>
|
|
<div class="m-credits">
|
|
<div class="m-credit">
|
|
<span class="m-credit-label">Backed by</span>
|
|
<span class="m-credit-name">Innofounder</span>
|
|
<span class="m-credit-auth">Innovationsfonden</span>
|
|
</div>
|
|
<div class="m-credit">
|
|
<span class="m-credit-label">Part of</span>
|
|
<span class="m-credit-name">AI Lab</span>
|
|
<span class="m-credit-auth">BioInnovation Institute</span>
|
|
</div>
|
|
<div class="m-credit">
|
|
<span class="m-credit-label">Part of</span>
|
|
<span class="m-credit-name">The AI Regulatory Sandbox</span>
|
|
<span class="m-credit-auth">Datatilsynet & Digitaliseringsstyrelsen</span>
|
|
</div>
|
|
</div>
|
|
</section>
|
|
|
|
<!-- ─── Project Bifrost reveal ───
|
|
The aurora arc from the desktop hero, held still as a cropped
|
|
backdrop. Sized wider than the viewport so the arc runs off
|
|
both edges rather than shrinking into a thin ribbon. Drawn
|
|
once, static — no GSAP, no scrub. -->
|
|
<section class="m-section m-bifrost">
|
|
<div class="m-bifrost-arc" aria-hidden="true">
|
|
<svg viewBox="0 0 1400 500" preserveAspectRatio="xMidYMid meet" xmlns="http://www.w3.org/2000/svg">
|
|
<defs>
|
|
<linearGradient id="mAurora" x1="0" x2="1" y1="0" y2="0">
|
|
<stop offset="0%" stop-color="#b48755" stop-opacity="0"/>
|
|
<stop offset="15%" stop-color="#b48755" stop-opacity="0.95"/>
|
|
<stop offset="40%" stop-color="#a4553b" stop-opacity="0.95"/>
|
|
<stop offset="65%" stop-color="#5c7b8e" stop-opacity="0.95"/>
|
|
<stop offset="85%" stop-color="#6e5a86" stop-opacity="0.95"/>
|
|
<stop offset="100%" stop-color="#6e5a86" stop-opacity="0"/>
|
|
</linearGradient>
|
|
<linearGradient id="mAuroraSoft" x1="0" x2="1" y1="0" y2="0">
|
|
<stop offset="0%" stop-color="#b48755" stop-opacity="0"/>
|
|
<stop offset="15%" stop-color="#b48755" stop-opacity="0.28"/>
|
|
<stop offset="40%" stop-color="#a4553b" stop-opacity="0.28"/>
|
|
<stop offset="65%" stop-color="#5c7b8e" stop-opacity="0.28"/>
|
|
<stop offset="85%" stop-color="#6e5a86" stop-opacity="0.28"/>
|
|
<stop offset="100%" stop-color="#6e5a86" stop-opacity="0"/>
|
|
</linearGradient>
|
|
<filter id="mSoftGlow" x="-20%" y="-50%" width="140%" height="200%">
|
|
<feGaussianBlur stdDeviation="10"/>
|
|
</filter>
|
|
</defs>
|
|
<path d="M 60 420 Q 700 -40 1340 420"
|
|
fill="none" stroke="url(#mAuroraSoft)"
|
|
stroke-width="28" stroke-linecap="round"
|
|
filter="url(#mSoftGlow)"/>
|
|
<path d="M 60 420 Q 700 -40 1340 420"
|
|
fill="none" stroke="url(#mAurora)"
|
|
stroke-width="3" stroke-linecap="round"/>
|
|
<path d="M 80 420 Q 700 -20 1320 420"
|
|
fill="none" stroke="url(#mAurora)"
|
|
stroke-width="1" stroke-linecap="round" opacity="0.6"/>
|
|
</svg>
|
|
</div>
|
|
<div class="m-bifrost-content">
|
|
<p class="m-bifrost-eyebrow">Introducing</p>
|
|
<h2 class="m-bifrost-name">Project <em>Bifrost</em></h2>
|
|
<p class="m-bifrost-sub">
|
|
The bridge <em>between</em> an industrial-grade AI platform and the realities of regulated organisations — built <em>with</em> them, not just for them.
|
|
</p>
|
|
</div>
|
|
</section>
|
|
|
|
<!-- ─── What Project Bifrost means ─── -->
|
|
<section class="m-section m-meaning" aria-labelledby="m-meaning-head">
|
|
<p class="m-section-eyebrow">The invitation</p>
|
|
<h2 id="m-meaning-head" class="m-section-head">
|
|
What being part of <em>Project Bifrost</em> means
|
|
</h2>
|
|
<p class="m-meaning-lede">
|
|
Three ways to <em>shape</em>, to <em>influence</em>, and to <em>build with</em> the platform from the inside.
|
|
</p>
|
|
|
|
<article class="m-stop">
|
|
<img class="m-stop-illust" src="/fenja/illustrations/community.svg" alt="" aria-hidden="true" />
|
|
<p class="m-stop-eyebrow">Be part of a</p>
|
|
<h3 class="m-stop-title"><em>Community</em></h3>
|
|
<p class="m-stop-sub">Shape the future together</p>
|
|
<p class="m-stop-body">Join a select community of organisations helping define the future of trusted sovereign AI in Denmark and Europe. At a time when Europe needs greater technological independence, this is an opportunity to contribute to an AI platform built on trust, shared ambition, and a common mission.</p>
|
|
</article>
|
|
|
|
<article class="m-stop">
|
|
<img class="m-stop-illust" src="/fenja/illustrations/council.svg" alt="" aria-hidden="true" />
|
|
<p class="m-stop-eyebrow">Be part of an</p>
|
|
<h3 class="m-stop-title"><em>Advisory Council</em></h3>
|
|
<p class="m-stop-sub">Turn insight into influence</p>
|
|
<p class="m-stop-body">Take part in regular advisory council sessions where your input directly shapes the product and platform roadmap. Gain first-hand insight into cutting-edge AI developments and help influence what is built, which capabilities are prioritised, and how the platform evolves to meet real organisational needs.</p>
|
|
</article>
|
|
|
|
<article class="m-stop">
|
|
<img class="m-stop-illust" src="/fenja/illustrations/pilot.svg" alt="" aria-hidden="true" />
|
|
<p class="m-stop-eyebrow">Be part of</p>
|
|
<h3 class="m-stop-title"><em>Pilot Projects</em></h3>
|
|
<p class="m-stop-sub">Access the platform before others</p>
|
|
<p class="m-stop-body">A select number of Project Bifrost participants will have the opportunity to join pilot projects and gain early access to the platform at a significantly reduced price, subsidised by the Innovation Fund. This gives your organisation the chance to explore cutting-edge sovereign AI early, realise value at low cost, and help shape the platform through real-world use.</p>
|
|
</article>
|
|
</section>
|
|
|
|
<!-- ─── Advisory board ─── -->
|
|
<section class="m-section m-board" aria-labelledby="m-board-head">
|
|
<h2 id="m-board-head" class="m-section-head">Meet the Fenja AI <em>Advisory Board</em></h2>
|
|
<p class="m-board-sub">Bridging industry & sovereign AI</p>
|
|
|
|
<div class="m-board-grid">
|
|
<figure class="m-board-member">
|
|
<div class="m-board-portrait"><img src="/fenja/board/soren-friis.jpg" alt="Søren Friis" loading="lazy" /></div>
|
|
<p class="m-bm-name">Søren Friis</p>
|
|
<p class="m-bm-title">IT Director</p>
|
|
<p class="m-bm-company">DSB</p>
|
|
</figure>
|
|
|
|
<figure class="m-board-member">
|
|
<div class="m-board-portrait"><img src="/fenja/board/william-irving.jpg" alt="William Irving" loading="lazy" /></div>
|
|
<p class="m-bm-name">William Irving</p>
|
|
<p class="m-bm-title">Chief Data & Analytics Officer</p>
|
|
<p class="m-bm-company">Norlys</p>
|
|
</figure>
|
|
|
|
<figure class="m-board-member">
|
|
<div class="m-board-portrait"><img src="/fenja/board/ulla-nygaard-eliassen.jpg" alt="Ulla Nygaard Eliassen" loading="lazy" /></div>
|
|
<p class="m-bm-name">Ulla Nygaard Eliassen</p>
|
|
<p class="m-bm-title">Associate Improvement Project Director</p>
|
|
<p class="m-bm-company">Novo Nordisk</p>
|
|
</figure>
|
|
|
|
<figure class="m-board-member">
|
|
<div class="m-board-portrait"><img src="/fenja/board/anna-jessen.jpg" alt="Anna Jessen" loading="lazy" /></div>
|
|
<p class="m-bm-name">Anna Jessen</p>
|
|
<p class="m-bm-title">Director, Process Excellence & Digitalization</p>
|
|
<p class="m-bm-company">Novo Nordisk</p>
|
|
</figure>
|
|
|
|
<figure class="m-board-member">
|
|
<div class="m-board-portrait"><img src="/fenja/board/mathies-laursen.jpg" alt="Mathies Laursen" loading="lazy" /></div>
|
|
<p class="m-bm-name">Mathies Laursen</p>
|
|
<p class="m-bm-title">CDO</p>
|
|
<p class="m-bm-company">Nationalbanken</p>
|
|
</figure>
|
|
|
|
<figure class="m-board-member">
|
|
<div class="m-board-portrait"><img src="/fenja/board/torben-schutt.jpg" alt="Torben Schütt" loading="lazy" /></div>
|
|
<p class="m-bm-name">Torben Schütt</p>
|
|
<p class="m-bm-title">Office Director, Center for Cyber and Digitalization</p>
|
|
<p class="m-bm-company">Forsvarsministeriet</p>
|
|
</figure>
|
|
|
|
<figure class="m-board-member">
|
|
<div class="m-board-portrait"><img src="/fenja/board/mads-nyborg.jpg" alt="Mads Nyborg" loading="lazy" /></div>
|
|
<p class="m-bm-name">Mads Nyborg</p>
|
|
<p class="m-bm-title">Chief Consultant, Department of Data and Analytics</p>
|
|
<p class="m-bm-company">Københavns Kommune</p>
|
|
</figure>
|
|
|
|
<figure class="m-board-member">
|
|
<div class="m-board-portrait"><img src="/fenja/board/hakon-daltveit.jpg" alt="Håkon Daltveit" loading="lazy" /></div>
|
|
<p class="m-bm-name">Håkon Daltveit</p>
|
|
<p class="m-bm-title">Chief Consultant, Department of Data and Analytics</p>
|
|
<p class="m-bm-company">Københavns Kommune</p>
|
|
</figure>
|
|
</div>
|
|
</section>
|
|
|
|
<!-- ─── Platform question (framing) ───
|
|
Mirrors desktop #platform-question — the lead-in that reframes
|
|
"rent capabilities / install a model" as not enough. -->
|
|
<section class="m-section m-pq">
|
|
<h2 class="m-pq-title">
|
|
Renting a few AI capabilities from American companies isn’t enough. Installing an open-source language model isn’t enough.
|
|
</h2>
|
|
<p class="m-pq-body">
|
|
You need a <em>platform you control</em> — with the tools, the knowledge, and the framework to make AI actually do the work your organization needs done.
|
|
</p>
|
|
</section>
|
|
|
|
<!-- ─── Architecture ───
|
|
Static flatten of desktop #platform-layers: the five narrative
|
|
beats as colored cards, then the component grid (Foundation /
|
|
Tools / Agents) under an "Everything Client-Managed" frame. -->
|
|
<section class="m-section m-arch" aria-labelledby="m-arch-head">
|
|
<p class="m-section-eyebrow">Fenja AI Platform Architecture</p>
|
|
<h2 id="m-arch-head" class="m-section-head">Simply <em>explained.</em></h2>
|
|
|
|
<article class="m-arch-beat">
|
|
<p class="m-arch-eyebrow">The foundation</p>
|
|
<h3 class="m-arch-headline"><em>A model in your environment.</em></h3>
|
|
<p class="m-arch-body">A state-of-the-art open-source language model, running entirely on your hardware. No data leaves your perimeter. The starting point — but not yet Fenja.</p>
|
|
</article>
|
|
|
|
<article class="m-arch-beat">
|
|
<p class="m-arch-eyebrow">The foundation</p>
|
|
<h3 class="m-arch-headline"><em>Knowledge.</em></h3>
|
|
<p class="m-arch-body">What makes the model <em>Fenja</em> — an understanding of your organization, captured in a wiki your team can read and edit. Plus the routines and working memory that turn Fenja into a coworker who knows how things get done.</p>
|
|
</article>
|
|
|
|
<article class="m-arch-beat">
|
|
<p class="m-arch-eyebrow">What Fenja can do</p>
|
|
<h3 class="m-arch-headline"><em>Tools.</em></h3>
|
|
<p class="m-arch-body">How knowledge becomes work. Fenja uses tools to find documents, query data, take action across your systems. Some are obvious; others depend on what your work needs.</p>
|
|
</article>
|
|
|
|
<article class="m-arch-beat">
|
|
<p class="m-arch-eyebrow">When one becomes a team</p>
|
|
<h3 class="m-arch-headline"><em>Agents.</em></h3>
|
|
<p class="m-arch-body">Real work isn’t one task. Fenja becomes a team — a supervisor and specialists, each focused, each governed, all dispatched by workflows you’ve designed.</p>
|
|
</article>
|
|
|
|
<article class="m-arch-beat m-arch-beat--summary">
|
|
<p class="m-arch-eyebrow">The full picture</p>
|
|
<h3 class="m-arch-headline"><em>Everything you need and with full control.</em></h3>
|
|
<p class="m-arch-body">Fenja brings together all the pieces to solve simple and complex AI use cases across your organisation. Every component hosted in your infrastructure with full traceability and governance. Secure and sovereign by design.</p>
|
|
</article>
|
|
|
|
<!-- Component grid — three labeled groups under the client-managed frame. -->
|
|
<div class="m-arch-frame">
|
|
<p class="m-arch-frame-label">Everything Client-Managed</p>
|
|
|
|
<div class="m-arch-group">
|
|
<div class="m-arch-group-head">
|
|
<span class="m-arch-group-label">Foundation</span>
|
|
<span class="m-arch-group-caption">Sovereign by design</span>
|
|
</div>
|
|
<div class="m-arch-cards">
|
|
<article class="m-arch-card">
|
|
<h4 class="m-arch-card-name">Language model</h4>
|
|
<p class="m-arch-card-italic">State-of-the-art, open-source</p>
|
|
<p class="m-arch-card-mono">On-prem</p>
|
|
</article>
|
|
<article class="m-arch-card">
|
|
<h4 class="m-arch-card-name">Wiki</h4>
|
|
<p class="m-arch-card-italic">Company and domain knowledge</p>
|
|
<p class="m-arch-card-mono">Organizational · Departmental · Personal</p>
|
|
</article>
|
|
<article class="m-arch-card">
|
|
<h4 class="m-arch-card-name">Routines & memory</h4>
|
|
<p class="m-arch-card-italic">How Fenja works inside it</p>
|
|
<p class="m-arch-card-mono">Stand-ups · Recurring tasks · Working memory</p>
|
|
</article>
|
|
</div>
|
|
</div>
|
|
|
|
<div class="m-arch-group">
|
|
<div class="m-arch-group-head">
|
|
<span class="m-arch-group-label">Tools</span>
|
|
<span class="m-arch-group-caption">How Fenja acts</span>
|
|
</div>
|
|
<div class="m-arch-cards">
|
|
<article class="m-arch-card">
|
|
<h4 class="m-arch-card-name">Document retrieval</h4>
|
|
<p class="m-arch-card-italic">Find and cite</p>
|
|
<p class="m-arch-card-mono">RAG</p>
|
|
</article>
|
|
<article class="m-arch-card">
|
|
<h4 class="m-arch-card-name">Structured data (ie SQL)</h4>
|
|
<p class="m-arch-card-italic">Query and extract</p>
|
|
<p class="m-arch-card-mono">NL → SQL</p>
|
|
</article>
|
|
<article class="m-arch-card">
|
|
<h4 class="m-arch-card-name">System actions</h4>
|
|
<p class="m-arch-card-italic">Read and write</p>
|
|
<p class="m-arch-card-mono">APIs · integrations</p>
|
|
</article>
|
|
<article class="m-arch-card">
|
|
<h4 class="m-arch-card-name">Custom tools</h4>
|
|
<p class="m-arch-card-italic">Your specific work</p>
|
|
<p class="m-arch-card-mono">Defined by you</p>
|
|
</article>
|
|
</div>
|
|
</div>
|
|
|
|
<div class="m-arch-group">
|
|
<div class="m-arch-group-head">
|
|
<span class="m-arch-group-label">Agents</span>
|
|
<span class="m-arch-group-caption">How Fenja scales</span>
|
|
</div>
|
|
<div class="m-arch-cards">
|
|
<article class="m-arch-card">
|
|
<h4 class="m-arch-card-name">Supervisor</h4>
|
|
<p class="m-arch-card-italic">Plan and dispatch</p>
|
|
<p class="m-arch-card-mono">Orchestration</p>
|
|
</article>
|
|
<article class="m-arch-card">
|
|
<h4 class="m-arch-card-name">Specialists</h4>
|
|
<p class="m-arch-card-italic">Focused expertise</p>
|
|
<p class="m-arch-card-mono">Subagents</p>
|
|
</article>
|
|
<article class="m-arch-card">
|
|
<h4 class="m-arch-card-name">Skills</h4>
|
|
<p class="m-arch-card-italic">Reusable capability</p>
|
|
<p class="m-arch-card-mono">Portable across specialists</p>
|
|
</article>
|
|
<article class="m-arch-card">
|
|
<h4 class="m-arch-card-name">Workflows</h4>
|
|
<p class="m-arch-card-italic">Composed by you</p>
|
|
<p class="m-arch-card-mono">Governed end-to-end</p>
|
|
</article>
|
|
</div>
|
|
</div>
|
|
</div>
|
|
</section>
|
|
|
|
<!-- ─── Wiki deep-dive ───
|
|
Static flatten of desktop #wiki-deepdive: scattered knowledge →
|
|
AI Compiler → structured output, top-to-bottom with chevron
|
|
connectors. Top stays "messy", bottom stays "calm". -->
|
|
<section class="m-section m-wiki" aria-labelledby="m-wiki-head">
|
|
<p class="m-section-eyebrow">From scattered to structured</p>
|
|
<h2 id="m-wiki-head" class="m-section-head">One structured <em>source of truth.</em></h2>
|
|
|
|
<div class="m-wiki-zone m-wiki-zone--scatter">
|
|
<p class="m-wiki-eyebrow">What you have today</p>
|
|
<h3 class="m-wiki-name">Scattered knowledge</h3>
|
|
<p class="m-wiki-sub">Documents · Emails · Notes · Knowledge in people’s heads</p>
|
|
</div>
|
|
|
|
<div class="m-wiki-arrow" aria-hidden="true"></div>
|
|
|
|
<div class="m-wiki-zone m-wiki-zone--compiler">
|
|
<p class="m-wiki-eyebrow">Fenja Compiler</p>
|
|
<h3 class="m-wiki-name">AI Compiler</h3>
|
|
<p class="m-wiki-sub">Apply your rules and structure to fit your requirements</p>
|
|
</div>
|
|
|
|
<div class="m-wiki-arrow" aria-hidden="true"></div>
|
|
|
|
<div class="m-wiki-zone m-wiki-zone--output">
|
|
<p class="m-wiki-eyebrow">Fenja Wiki</p>
|
|
<h3 class="m-wiki-name">Structured output</h3>
|
|
<p class="m-wiki-sub">Structured output · easy for humans and AIs to read.</p>
|
|
</div>
|
|
</section>
|
|
|
|
<!-- ─── Deployment options ───
|
|
Mirrors desktop #platform-cards "Choose your Capability". -->
|
|
<section class="m-section m-deploy" aria-labelledby="m-deploy-head">
|
|
<p class="m-section-eyebrow">Deployment options</p>
|
|
<h2 id="m-deploy-head" class="m-section-head">Choose your <em>Capability.</em></h2>
|
|
|
|
<div class="m-deploy-grid">
|
|
<article class="m-deploy-card">
|
|
<h3 class="m-deploy-name">Fenja <em>Core.</em></h3>
|
|
<p class="m-deploy-tier">Foundational</p>
|
|
<p class="m-deploy-body">Essential LLM capabilities with Fenja Semantic. Your safe and custom chatbot that understands your organization.</p>
|
|
</article>
|
|
|
|
<article class="m-deploy-card">
|
|
<h3 class="m-deploy-name">Fenja <em>Dev.</em></h3>
|
|
<p class="m-deploy-tier">Developer toolset</p>
|
|
<p class="m-deploy-body">Code faster and better with your own secure AI-supported development platform.</p>
|
|
<p class="m-deploy-includes">+ Core</p>
|
|
</article>
|
|
|
|
<article class="m-deploy-card">
|
|
<h3 class="m-deploy-name">Fenja <em>Analyze.</em></h3>
|
|
<p class="m-deploy-tier">Strategic intel</p>
|
|
<p class="m-deploy-body">Bring real insights to your people. You ask for an insight, and your agents will find, analyze, and present the relevant data.</p>
|
|
<p class="m-deploy-includes">+ Core</p>
|
|
</article>
|
|
|
|
<article class="m-deploy-card m-deploy-card--dark">
|
|
<h3 class="m-deploy-name">Fenja <em>Agentic.</em></h3>
|
|
<p class="m-deploy-tier">Automation</p>
|
|
<p class="m-deploy-body">The complete framework. Fully governed and controlled agents collaborate to solve your most important processes.</p>
|
|
<p class="m-deploy-includes">+ Core. Dev. Analyze.</p>
|
|
</article>
|
|
</div>
|
|
</section>
|
|
|
|
<!-- ─── Implementation roadmap ───
|
|
Mirrors desktop #platform-roadmap. Setup is the one-time
|
|
foundation; Knowledge / Tools / Agents are waves of use cases.
|
|
Cards are native <details> so they expand with no JS. -->
|
|
<section class="m-section m-roadmap" aria-labelledby="m-roadmap-head">
|
|
<p class="m-section-eyebrow">Implementation roadmap</p>
|
|
<h2 id="m-roadmap-head" class="m-section-head">One foundation, <em>many use cases.</em></h2>
|
|
|
|
<details class="m-rm-card">
|
|
<summary class="m-rm-summary">
|
|
<span class="m-rm-name">Setup</span>
|
|
<span class="m-rm-italic">Platform live in your environment</span>
|
|
</summary>
|
|
<div class="m-rm-detail">
|
|
<p class="m-rm-intro">The one-time foundation. In a single sprint, the platform goes live inside your infrastructure — model deployed, identity wired in, brand voice applied, baseline policies enforced. After this, the platform is ready to receive any use case.</p>
|
|
<p class="m-rm-label">Key activities</p>
|
|
<ul class="m-rm-list">
|
|
<li>Foundation model installed in your environment</li>
|
|
<li>SSO and identity provider connected</li>
|
|
<li>Brand voice, tone, and visual style applied</li>
|
|
<li>Baseline governance and security policies in place</li>
|
|
</ul>
|
|
</div>
|
|
</details>
|
|
|
|
<details class="m-rm-card">
|
|
<summary class="m-rm-summary">
|
|
<span class="m-rm-name">Knowledge</span>
|
|
<span class="m-rm-italic">Captured into one structured source</span>
|
|
</summary>
|
|
<div class="m-rm-detail">
|
|
<p class="m-rm-intro">The first body of use cases captures what your organisation already knows. For each use case, the team scopes the target output, ingests the right files, and runs AI-led interviews to surface the knowledge that today lives only in people’s heads.</p>
|
|
<p class="m-rm-label">Key activities</p>
|
|
<ul class="m-rm-list">
|
|
<li>Use case scope and target output defined</li>
|
|
<li>Relevant files ingested and structured</li>
|
|
<li>AI-led interviews capture tacit expert knowledge</li>
|
|
<li>Outputs tested and validated against real work</li>
|
|
</ul>
|
|
</div>
|
|
</details>
|
|
|
|
<details class="m-rm-card">
|
|
<summary class="m-rm-summary">
|
|
<span class="m-rm-name">Tools</span>
|
|
<span class="m-rm-italic">Acting across your systems</span>
|
|
</summary>
|
|
<div class="m-rm-detail">
|
|
<p class="m-rm-intro">Use cases that reach beyond knowledge into your systems. Each tool implementation wires the platform into a specific source or destination — a data warehouse, a SharePoint repository, an API, a structured report. The platform stops being read-only and starts acting on your behalf.</p>
|
|
<p class="m-rm-label">Key activities</p>
|
|
<ul class="m-rm-list">
|
|
<li>Ongoing retrieval from data warehouses and SharePoint</li>
|
|
<li>Read and write integrations to specific APIs</li>
|
|
<li>Custom report outputs and structured deliverables</li>
|
|
<li>Each tool scoped, built, and tested for one specific job</li>
|
|
</ul>
|
|
</div>
|
|
</details>
|
|
|
|
<details class="m-rm-card">
|
|
<summary class="m-rm-summary">
|
|
<span class="m-rm-name">Agents</span>
|
|
<span class="m-rm-italic">Workflows running under your control</span>
|
|
</summary>
|
|
<div class="m-rm-detail">
|
|
<p class="m-rm-intro">Use cases that compose multiple steps into one governed workflow. For each agent use case, the team defines the task, builds the specialist agents that handle it, and configures monitoring, human checkpoints, and governance at every step. The platform now does work end to end — under your control.</p>
|
|
<p class="m-rm-label">Key activities</p>
|
|
<ul class="m-rm-list">
|
|
<li>Agent tasks defined and scoped per workflow</li>
|
|
<li>Specialist agents built for specific jobs</li>
|
|
<li>Monitoring and audit trails configured</li>
|
|
<li>Human-in-the-loop checkpoints placed where they matter</li>
|
|
<li>Governance and security checks enforced at each step</li>
|
|
</ul>
|
|
</div>
|
|
</details>
|
|
|
|
<div class="m-rm-band">
|
|
<p class="m-rm-band-name">Govern & scale</p>
|
|
<p class="m-rm-band-italic">Security · compliance · change management · training · advisory council feedback</p>
|
|
</div>
|
|
|
|
<p class="m-rm-foot">Setup is bounded · waves of use cases continue as your needs evolve.</p>
|
|
</section>
|
|
|
|
</main>
|
|
|
|
<script src="/mobile/mobile.js" defer></script>
|
|
|
|
</body>
|
|
</html>
|