People before machinery.
Begin with the person, their context and their intended outcome. Keep everyday interaction clear, with depth available when it is useful.
ENGINEER · AUTOMATE · SCALEEngineering a more
Engineering a more
capable tomorrow.
We are Keddeh Systems, a technology and engineering company developing connected intelligence, software and virtual environments. Our ambition is to help people do more with technology they can understand, direct and trust.
IL‑LLMMeaning, relationships & context
BRAINKActions, authority & continuity
KEXState, addressing & mechanics
Distinct technologies. Connected architecture.
INTELLIGENCE & EXECUTIONVIRTUAL ENVIRONMENTSSOFTWARE & SERVICES18 INDEPENDENT FOUNDRIES
Who we are · What we stand forHuman purpose.
Human purpose.
Engineering depth.
We believe technology should expand what people can accomplish, while keeping them informed and in control.
What we do
Keddeh Systems develops software, computational technologies and connected working environments. Our work spans semantic intelligence, governed execution, virtual workstations and desktops, customer applications, and the services that connect them.
BRAINK, IL‑LLM and KEX each address a different part of that architecture. Our 18 independent foundries bring specialist research, engineering, delivery and human experience into collaboration.
Explore the company →What we envision
A computing experience where knowledge can become useful action, work can continue across environments, and complex capabilities remain understandable to the people using them.
That is our direction, not a claim that every part is already complete. We show what is available, explain what is being developed, and make room for scrutiny and improvement.
See the projects behind the vision →Substance behind the claim.
Connect explanations to mechanisms and evidence. Distinguish an idea, an implementation, an observed result and an independent assessment.
Connection with integrity.
Bring systems together while preserving their identities, responsibilities and boundaries. Improve through research, critique and accountable engineering.
Start with your outcomeWhat would you like
What would you like
to make possible?
Choose the work that matters. We’ll help you describe the outcome and identify the relevant technology and delivery questions.
Make knowledge useful
in the flow of work.
Explore how relationships, context and addressable information can connect what your organisation knows to what it needs to do.
Scope a knowledge challenge →Turn a process into
an accountable service.
Map the trigger, responsibilities, actions, exceptions and evidence. Keep the human outcome visible throughout the workflow.
Scope a service workflow →Give complex technology
a usable environment.
Explore software, virtual workstations and desktop experiences that bring capabilities together around real tasks.
Scope an environment →The technology, in contextComplex underneath.
Complex underneath.
Clear where you use it.
Each technology keeps its own role. Explore the mechanics when you need them, without making them the price of entry.
IL‑LLM / RELATIONAL SUBSTRATEFollow the relationships.
Explore IL‑LLM architecture →
Follow the relationships.
Keep the context.
IL‑LLM connects addressable concepts and system objects through typed relationships. Its inspected runtime includes route traversal and continuation state; ServerSpace also contains weighted relation mechanics.
Try a bounded example: change a relationship, observe decay and remove weak associations. The displayed value is a relation weight, not a probability that a statement is true.
What does this demonstrate about learning?
This executes relation binding, decay and pruning from the supplied IL‑LLM relation component. You provide the updates. It demonstrates mutable associative state, not autonomous learning, trained-model improvement or a benchmark of intelligence. Those broader claims require separate evidence.
Interactive relation experiment
Customer need → Service response
0.400
Association strength · local to this page
Starting relation: 0.400. Change it to see the result.
Mechanism and scope
Reuses ILLLMRelationSubstrate from ServerSpace. Strengthen sets the current weight + 0.15, bounded at 1. Decay reduces it by 25%. Prune removes a weight below 0.3. No input is transmitted, and reloading resets this experiment.
BRAINK / GOVERNED EXECUTIONKeep the action connected
Keep the action connected
to its authority and result.
BRAINK coordinates registered capabilities, dependencies and continuation. Its execution layer distinguishes an available handler from a capability that has only been described.
- Identify the action and its permitted scope.
- Resolve dependencies and execute through the bound handler.
- Retain work results and context for further action.
- Keep independent assessment separate from worker output.
KEX / STATE & COMPUTATIONGive transitions
Explore KEX →
Give transitions
an explicit structure.
KEX concerns state geometry, addressing, seeds and engines. The inspected runtime includes a bounded compiler, intermediate representation, executable packaging, loading and logical scheduling.
How does the construction chain fit together?
Word → node → node equipped with VFS → IL‑LLM → bootstrapper → compiler → assembler → KEX seed → KEX engines → IL‑LLM module of KEX seeds. Each stage retains its own meaning. A source mapping alone does not establish execution of the entire chain.
VIRTUAL ENVIRONMENTS / WORKSTATIONS / DESKTOPSBring capabilities together
Bring capabilities together
without losing their identity.
The architectural aim is continuity across environments: knowledge, tools, state, applications and work can be connected while their identities and responsibilities remain distinct.
ServerSpace provides a substantial browser environment for exploring virtual servers, desktops and runtime tools. Physical host operations depend on their connected adapters; an interface control alone does not establish a remote effect.
Explore the environment projects →WORKBOOK SUBSTRATES / VFS / CONTINUATIONCarry state through
Explore the full foundry fabric →
Carry state through
the work.
Workbook-native computation, VFS identities and continuation are distinct parts of the wider architecture. The resident runtime includes snapshot and restoration mechanics that preserve object relationships.
What does coexistence mean here?
Multiple logical environments may share a host while retaining separate identities, state and routes. Creating a logical environment does not multiply physical compute. Durability and isolation must be established at the actual storage and execution boundaries.
Projects with substanceExplore the work.
Explore the work.
Understand what it does.
Open a product, examine an architectural capability, or go deeper into a project’s purpose and operating boundaries.
ClaimPath
A browser application for organising a claim inventory and preparing a printable report.
Purpose, experience and boundaries
Start with the details you need to organise, build an inventory and review the resulting report. The interface supports the organisation task; it does not establish claim eligibility, an insurer’s decision or a legal outcome. Check the app’s storage behaviour before relying on it for your only copy.
KEX
Explore state, addressing and computational interactions in the existing browser application.
Mechanics and evaluation
KEX covers a wider architectural estate than this application. Its compiler, seed, engine and state mechanics remain separate concepts. Evaluate a particular function using its inputs, output, source and target runtime; a browser demonstration is not evidence for every deployment target.
BRAINK
A governed fabric for capabilities, dependencies, execution and continuity.
What to inspect
Inspect how an action resolves to its handler, what state changes, and what evidence is retained. Operational flags, work tickets, results, independent assessments and receipts are separate objects. The owner console is an authenticated operating environment.
ServerSpace
Virtual server, workstation and desktop surfaces bring runtime tools into a connected environment.
What runs where?
The supplied application includes browser-executed relation, memory and compute components. Host installation, reboot and service operations require a real connected executor. The current operational environment is accessed through the owner workspace.
A distinct service estate.
Visit CasePath’s existing website to explore its own service information and customer journey.
Independent product identity
CasePath and ClaimPath remain distinct. Check CasePath’s published service scope, applicable terms and contact route on its own site. Its identity and customer relationship are not collapsed into the Keddeh technology console.
The foundry fabric
18 independent foundries connect research, engineering, delivery and human experience.
Depth without collapse
Frontage, Website, Service, HCI, Agentics, Workspace and the other foundries retain their own domain, methods and responsibilities. Their collaboration supports the company’s technology and services; a directory entry is not a claim that every service is commercially available.
A useful next stepStart with the challenge.
Start with the challenge.
Make the next step clear.
Tell us what you want to change. Build a concise enquiry around your current situation, intended outcome and constraints.
You can review the brief before opening your email app. Nothing is submitted automatically, and this form does not upload your information.
What should I include?
The task people are trying to complete, where it breaks down, the systems involved, and what a useful result would look like. Leave out passwords, access tokens and sensitive customer records.
Questions worth asking
Depth you can inspect.
Clear answers about the technology, its evidence and the experience you can expect.
What is different about Keddeh’s approach?
The architecture connects semantic relationships, governed execution, computational state and virtual environments while retaining their distinct roles. That combination is a candidate source of value. Comparative performance or paradigm-shift claims need specific workloads, strong baselines and independent assessment.
Is the relation experiment proof that the system learns autonomously?
No. It runs actual relation-update mechanics from the supplied source, driven by your actions. It shows state changing in response to explicit inputs. Autonomous learning requires an identified learning rule, data, evaluation and evidence of improvement; this experiment does not claim those results.
Can I use the products without understanding the architecture?
Yes. Product entry points are separated from technical explanations. Start with the task a product supports. Architecture, methods and operating boundaries remain available when they help you make a decision.
Does a completed task mean it has been independently verified?
No. A worker’s result and its supporting evidence are assessed separately. Under Keddeh’s process, the independent assessment team issues its report and receipt. A task status, hash or deployment message is not that assessment.
How do I discuss a service or technical partnership?
Use the enquiry builder above to describe your desired outcome. Review and send the brief to inquiries@keddeh.com. Scope, delivery, support and commercial terms need to be agreed for the actual engagement.
Interactive research
Explore static and adaptive coupling with reproducible simulations, paired trials and downloadable results.
Open the resonance experiment