Ein Client · Always on · Business Continuity
Business Continuity
Keep. Acting.
Whatever is down.
OUTAGE
OUTAGE
ID Austria · ELGA · DSGVO · EU-sourverän
Chat, Mail, Video, Files.
Your Team keeps moving
Your tenant is compromised, your system was shut down, a region just dropped.
But: The factory still runs, the site still builds, the patient keeps beeing treated.
KeenAct ist die souveräne Plattform, die Ihr gesamtes Microsoft 365, Webex und Co. permanent synchron vorhält. Aktiv nutzbar, oder unsichtbar im Hintergrund.
What's your fallback when Teams is down?
0
DOWNTIME
FOR YOUR OPERATIONS
Your people keep acting. Information still flows. Whatever is down behind the scenes.
0
SETUP
FOR YOUR TEAMS
Same client. Same login. Same files. Your teams don‘t switch tools. They keep acting.
0
BYTES
LOST
Encrypted. Identity-isolated. EU-hosted. Even when they‘re in your infrastructure, they‘re not in this one.
Continuitiy that is already active, not only after pressing a button.
WHEN IT HITS
Your Teams keep
acting.
Users, chats, calendar and files are mirrored continuously. Isolated and always on. Your context is already here.
PARALLEL · SOVEREIGN · CARRIER-GRADE
WÄHRENDDESSEN
Nothing to activate.
Nothing to switch.
The protocol in the background changes. Your teams continue with their full context, as if nothing ever happened.
IDENTITY ISOLATED · ALWAYS ON
BEIM AUDIT
Every action on
record.
NIS-2, DORA, your insurer. They want to know what you did. Every message. Every transcript. Every decision sealed and signed.
TAMPER-EVIDENT · SIGNED · IMMUTABLE
Wenn es passiert
WHEN IT HITS
Your Teams keep
acting.
Ransomware. Regional outage. IdP abuse. The reason might be diverse. What stops is communication. Yours doesn't
ID AUSTRIA · VERIFIZIERT · ELAK KOMPATIBEL
Währenddessen
WÄHRENDDESSEN
Nothing to activate.
Nothing to switch.
KeenAct is always there. Always current. Your teams use it with their full context. Im gleichen It‘s like they never switched.
IDENTITY ISOLATED · ALWAYS ON
Beim Audit
BEIM AUDIT
Every action on
record.
NIS-2, DORA, your insurer. They want to know what you did. Every message. Every transcript. Every decision sealed and signed.
TAMPER-EVIDENT · SIGNED · IMMUTABLE
NIS-2
NIS-2 requires a fallback when your infrastructure is compromised.
KeenAct is purpose-built to be one. Always ready.
It mirrors your users and conversations. So it is up to date, when you need it!
CONTINUITY AS A SERVICE
One platform. Three tiers.
Your choice per workforce
Continuous sync from Microsoft 365, Webex & Co. Including Identities, Chats, Mails, Calendar and Files.
All your context ready for you when the incident happens.
CHATS
FILES
USERS
COLD
Login. Act.
Empty inbox.
WARM
Login. Act.
Your context.
HOT
Already here
Keep acting.
COLD
The emergency channel.
Fallback ready, logins prepared. Instant communication when all else fails.
Right-sized protection:
Accessible in an emergency, invisible day-to-day. Cost-effective
WARM
The synchronized fallback.
Chats, emails, and files are fully mirrored and available in real time.
Pick up exactly where you left off with complete context.
Best for:
Anyone who would be lost without their context.
HOT
Daily parallel operation.
The sovereign client is your active workspace. No need to switch in an emergency, because it‘s already in use.
For confidential conversations:
Daily use of the sovereign client, yet fully connected to everyone.
How it
Works.
What carries the platform, how the three products build on one another, and why the ability to act does not begin with the incident, it simply continues.
Three layers.
One principle: decoupling.
What carries the platform, how the three products build on one another, and why the ability to act does not begin with the incident, it simply continues. Was an einer Stelle ausfällt, reißt nichts anderes mit.
What fails in one place takes nothing else with it. KeenAct is not a silo of its own, but the tier that continuously mirrors what Hub and Collab carry into an isolated parallel operation.
KeenAct ist dabei kein eigenständiges Silo, sondern die Stufe, die das, was Hub und Collab führen, kontinuierlich in einen isolierten Parallelbetrieb spiegelt.
KeenHub
Identity
Layer 1
KeenCollab
Conversation, decoupled from the channel
Layer 2
KeenAct
Operation, decoupled from the primary system.
Layer 3
1 - The architecture
One architecture. Three states.
Two worlds running side by side, not one after the other.
- No rebuild, no migration. The sovereign environment grows alongside your estate, not in its place. Microsoft 365 remains the primary system.
- Event-driven, not periodic. Chats, channels, structure, files and calendars are taken over as they arise, not in backup windows.
- HOT users already work here. They stay visible, callable and invitable for their colleagues in Teams. For the other side, nothing changes.
- Separate infrastructure. Storage and services sit in a dedicated EU environment with no link to Microsoft 365 or Azure. Whoever is inside your tenant is still a long way from being inside this one.
2 - WHAT IS CONTINUOUSLY RECONCILED
Four data worlds. Four sets of rules.
A chat message behaves differently from a two-gigabyte deck, and that again differently from a recurring meeting with fourteen invitees. KeenAct treats each domain by its own logic, with one shared goal: When the incident comes, the context is already there.
Identity & users
Held centrally, signed in several ways
Users are created once centrally or taken over automatically, then provisioned to every target platform. Alternative sign-in paths are permanently in place and valid in parallel — not set up once an incident occurs.
What you get from it
You get in, even when the sign-in source itself has failed. A fallback whose door will not open is not a fallback.
Chats, channels & structure
Taken over as it happens
Messages, channels, team structure and the associated metadata are taken over event by event, at the moment they arise. Not on an interval, not as a nightly run.
What you get from it
In an outage you do not read a state reconstructed from last night, but the one from a moment ago. The thread does not break.
Files
Scattered where they are stored, captured in full
In Microsoft 365, files do not live in one place: chat attachments land in the sender's personal storage, channel files in a separate store per team. KeenAct discovers new storage locations on its own, takes over changes as they occur, and additionally reconciles in full once a day. Two mechanisms, not one.
What you get from it
In an outage the file is not merely present but still editable together, in the browser, in the usual Office formats.
Calendar & conferences
Meetings that survive the outage
Meetings are held with organiser, invitees and response status, recurring series resolved into their individual occurrences. A Teams meeting's join link depends on Microsoft 365 and is worthless in an outage — KeenAct replaces it with a join into the sovereign conference and maps the invitees to their sovereign identities.
What you get from it
The nine o'clock meeting happens at nine o'clock. Joined from the calendar — no new link, no all-staff email, no phone tree.
3 - Identity
The critical point of every failover.
Most fallback solutions fail not on the data but on the sign-in. When the vendor goes down, the directory the sign-in depends on goes with it. KeenGen solves that by decoupling.
Effect in everyday operation
The vendor becomes replaceable
Because the identity no longer lives inside the target system, changing vendor is a provisioning step rather than a migration project. That is your exit strategy at the same time — documented before you need it.
Effect in everyday operation
The sign-in keeps working
Several sign-in paths are permanently in place and available independently of Microsoft: the national identity service ID Austria, your own directory on premises, and credentials stored in advance. The user keeps their familiar identity.
4 - The moment of switching
5 clear steps. Fully automatic.
1
Detection
The outage is picked up by monitoring or triggered deliberately, for a planned failover exercise, for instance. The organisation decides when to switch, not the vendor.
2
Switch identity
Sign-in is routed to the alternative source. No new accounts, no break-glass users: the identities are already there and continuously current.
3
Users move
HOT users are productive without doing anything at all. WARM and COLD users open the provisioned client and sign in. No training needed, because it is the same interface.
4
Keep working
Chats, channels, files, calendars and conferences are ready, with full history depending on tier. Not in a reduced emergency mode, but at full functionality.
5
Keep the record
Everything created now is held in the sovereign environment and kept for the replay. Complete and tamper-evident — for NIS-2, DORA, your insurer and your own review.
5 - What the individual gets
You decide per user what is already there when it matters.
The difference between the tiers is not access to the system. Everyone gets in. The difference is what is waiting for them.
|
|
HOT
|
WARM
|
COLD
|
|---|---|---|---|
6 - Where the dependency ends
Sovereignty is verifiable, or it is not sovereignty.
A fallback that needs the same cloud as the system that just failed is not a fallback. So here is what runs where, openly.
Runs entirely in the sovereign environment
- Sign-in and identity management
- Chat, groups, channels and the full history — end-to-end encrypted, with no administrator access to content
- File storage and collaborative document editing in the usual Office formats
- Audio and video conferencing including moderation, sharing, breakout rooms and recording
- Calendar and meeting management
- Mirror and sovereign storage, operated in the EU
Touches Microsoft — and precisely here
- The bridge for presence, calls and conferences between the sovereign client and Teams. For that, and nothing else.
- It is created and operated inside the customer's own Azure subscription: region, data residency, budget and access stay in their hands. Access can be withdrawn at any time.
- Calls between sovereign users do not run over it. Chat, files, calendar and mirroring never touch it.
- When Microsoft goes down it drops out — with no effect, because there is then no Teams side left to reach.
Let's talk!
Send us a message - we're looking forward to hearing from you.
Not a fan of forms? Just send us an email: office@keengen.eu
