Start with real work.
A project to finish, a document to review, a concept to understand. Product development begins with a task that matters to the person doing it.
EMPHOS · The road ahead
This is only
the beginning.
Built for what
comes next.
A new language model. A workspace that carries work forward. Professional tools with a practical purpose. EMPHOS is building toward a wider family of software, services, and connected experiences.
Last updated:
AletheiaThe language model at the foundation of our AI development.
HeinrichThe workspace built around projects, conversations, and guided action.
DesktopMobile roadmap
Alongside our AI development
FieldLine PDFProfessional PDF software with its own product and commercial roadmap. The Windows desktop app includes local FLORA.
FieldLine PlannerSchedule planning on Windows, with local FLORA. Level resources stays a user command.
FieldLine ConstructionCompany-operated construction software. FLORA is in the Windows desktop app.
RightNow MaintenanceCompany-operated property maintenance. Desktop FLORA answers from the manual and does not read company records.
Long-term direction
More capability.
A clearer experience.
The ambition is to make useful intelligence part of how people work and learn. That means developing the model, the application, and the experience together, while giving each product a clear job to do.
Carry the context forward.
Build connections between conversations, decisions, and results so moving between sessions or devices becomes a natural part of the workflow.
Grow through focused steps.
Extend the work into mobile experiences, partner products, organizational deployments, and dedicated interfaces through defined development stages.
The development portfolio
Ten directions.
Room to go further.
Explore the product roadmaps, partner pathways, and longer-term concepts shaping EMPHOS. Each direction has its own priorities and next milestone.
Showing all 10 directions
01Model development
Aletheia
The intelligence at the foundation.
Aletheia is the EMPHOS language model. Its roadmap centres on improving language capability, carrying useful context through a conversation, and making CPU inference practical across a broader range of workloads.
- Evaluate response quality across repeatable language and reasoning tasks.
- Develop training, runtime, and inspection tools together.
- Measure latency, memory use, and energy alongside output quality.
Next milestone
Broader evaluation and a repeatable model-to-application development process.
02Workspace development
Heinrich desktop
Turn a request into reviewable work.
Heinrich brings Aletheia into a workspace built around projects, chats, local context, and tools. The next stage focuses on making multi-step work easier to direct, follow, check, and resume.
- Keep project context and conversations connected across sessions.
- Make proposed actions, permissions, and approvals clear.
- Improve output checks, saved artifacts, and records of completed actions.
Next milestone
A more dependable end-to-end experience from project setup to a checked result.
03Mobile planning
Heinrich mobile app
Keep the next decision within reach.
The mobile roadmap extends the Heinrich workspace to your phone. It focuses on the moments when you need to check progress, continue a discussion, review a result, or decide what happens next.
- Bring selected project updates and conversations into a mobile interface.
- Design clear approval and review flows for a smaller screen.
- Develop continuity between desktop work and mobile check-ins.
Next milestone
A connected mobile workflow built around project context and user control.
04Commercial preparation
FieldLine PDF
Professional document work, from review to delivery.
FieldLine PDF has its own product roadmap for PDF review, markup, and calibrated drawing measurement on Windows. The immediate commercial focus is a clear path from trying the software to purchasing, activating, and using it.
- Prepare a 30-day trial with no card required, starting at first activation.
- Complete the direct-purchase, download, activation, and device-management journey.
- Keep installation help and separately downloadable training current.
Next milestone
A verified customer journey covering trial, purchase, licensing, updates, and support.
05Available desktop software
FieldLine Planner
Plan the work, with guidance that stays local.
FieldLine Planner is Windows schedule software with FLORA in the desktop app. She explains tasks, links, calendars, progress, the critical path, and resource capacity. Level resources can delay a whole task that has slack and does not split tasks. FLORA does not run that command or rewrite assignments.
- Keep schedule edits with the person using Planner.
- Keep FLORA questions and replies on the computer.
- Publish the lifetime-seat offer and the current desktop package separately from this roadmap.
Next milestone
The published desktop offer stays current with the shipped application, including the lifetime seat and local guidance.
06Available desktop software
FieldLine Construction
A company-operated construction workspace.
FieldLine Construction is delivered for an organization-controlled server. FLORA is included in the Windows desktop application and answers from the installed construction guide. She does not change the project. Browser and mobile access do not include the local assistant.
- Keep project records in the company environment.
- Keep FLORA conversations on the desktop computer.
- State the one-time enterprise licence separately from hosting and installation work.
Next milestone
Customer deployments that keep the desktop assistant and the company server as separate paths.
07Available desktop software
RightNow Maintenance
Property maintenance, with a local desktop guide.
RightNow Maintenance is a company-operated maintenance system. FLORA is in the Windows desktop app. She answers from the RightNow manual, does not read company maintenance records, and does not send the conversation to EMPHOS or the company server.
- Keep maintenance records on the organization server.
- Keep FLORA limited to the installed manual on the desktop.
- Leave browser and Android apps without the local assistant.
Next milestone
Rollouts that keep desktop guidance separate from resident, worker, and server records.
08Learning concept
Prism
Learning that responds to the learner.
Prism is the learning direction within the EMPHOS roadmap. It explores how conversation, structured material, and continuity between sessions can support a more adaptable learning experience.
- Explore flexible pacing and different levels of explanation.
- Give learners a way to ask questions within a structured pathway.
- Work with educators on content, accessibility, and evaluation.
Next milestone
A focused learning prototype evaluated with people and organizations who would use it.
09Monitoring research
Shield
Make connected information easier to act on.
Shield is the longer-term monitoring and security research direction. The focus is on how signals from connected environments can be presented with useful context, clear priorities, and understandable controls.
- Explore integration patterns for sensors and monitoring systems.
- Study event review, notification quality, and user-directed escalation.
- Define privacy, permissions, and human oversight for each use case.
Next milestone
A bounded prototype with defined inputs, review steps, and testable behaviour.
10Deployment planning
Enterprise & private deployment
Bring the workspace into an organization’s environment.
Enterprise development explores how Heinrich and Aletheia could fit customer-controlled infrastructure. The work starts with an organization’s workflow, information boundaries, and operational requirements.
- Define on-premise and hosted deployment patterns.
- Plan identity, access controls, operational records, and administration.
- Develop scoped pilots with clear acceptance criteria.
Next milestone
An agreed pilot that demonstrates the workflow inside the intended operating environment.
11Partner development
Licensing & OEM
Build with EMPHOS technology.
The licensing roadmap creates a path for selected partners to integrate Aletheia, Heinrich, or both into their own offerings. Each integration begins with a specific product purpose and a supported technical scope.
- Define the runtime or workspace functions the partner needs.
- Develop integration documentation, support boundaries, and acceptance checks.
- Agree deployment scope, delivery milestones, and commercial terms.
Next milestone
A qualified integration path from technical review to a working partner implementation.
12Device concepts
Physical interfaces
Reach beyond the conventional screen.
Device research explores where dedicated interfaces could make intelligence more useful: at a desk, in a shared space, in the field, or through a wearable. Each direction starts with the task and the person using it.
- Explore audio, visual, handheld, and shared-display interactions.
- Develop prototypes around power, ergonomics, and accessible controls.
- Evaluate sensor inputs and connections to the wider software experience.
Next milestone
Task-specific prototypes that can be assessed in the environments they are designed for.
13Infrastructure planning
EMPHOS A1
Plan the capacity behind future services.
EMPHOS A1 is the long-term infrastructure proposal for supporting hosted services and a larger research programme. Its roadmap connects computing requirements with facility design, energy use, and operations.
- Measure server workloads and capacity before setting deployment scale.
- Develop site, power, connectivity, cooling, and facility requirements.
- Sequence engineering, financing, approvals, and commissioning.
Next milestone
A site-specific, technically measured plan for staged infrastructure development.
Research & development
Go deeper into
the questions that matter.
Our research programme connects model behaviour, system performance, and human interaction. Open a topic to explore the work behind the roadmap.
Language capability & evaluation
Develop repeatable ways to assess language quality, reasoning, instruction-following, and task completion. The focus is on understanding where the model works well and using that evidence to guide the next development cycle.
Context & project continuity
Study how useful information carries through conversations and longer-running work. Connect model context with application-level project memory, source material, and saved results so the user can understand what a response is based on.
CPU inference & runtime engineering
Improve the execution path between the trained model and useful output. Measure response latency, memory use, concurrency, and behaviour across representative machines and workloads, alongside the quality of the work produced.
Tools, permissions & output checks
Make multi-step activity easier to inspect. Research how an application plans work, asks for approval, uses tools, checks results, and communicates progress so the person directing it can make informed decisions.
Resource efficiency
Measure energy and computing resources within clearly defined workloads. Explore how runtime choices, hardware, cooling, and operating patterns affect the resources required to deliver useful work at different scales.
Accessible, cross-device interaction
Explore readable interfaces, alternative input, audio and visual presentation, and continuity between desktop and mobile. Evaluate interaction choices with the people and environments each experience is intended to serve.
Physical interfaces · Concept research
The right interface
for the setting.
A phone or desktop will suit many tasks. Dedicated interfaces open other possibilities for shared spaces, hands-busy work, and information gathered away from a desk.
Home & display interfaces
Explore dedicated desktop environments, television and shared-display access, and wall-mounted controls that make connected information easier to reach.
Audio & wearable interfaces
Investigate compact ways to receive information and interact through audio, visual, wrist-worn, or professional wearable formats.
Handheld & environmental tools
Explore how portable interfaces and sensor inputs could support field reference, environmental observation, and structured information capture.
Vehicle & monitoring interfaces
Study context-aware reference and event review within defined vehicle or monitoring workflows, with clear controls for the person using the system.
Application research
Find the right problem.
Build around it.
The next applications begin with a specific workflow and the people who understand it. These research areas create a starting point for focused collaboration and pilot design.
Education & accessibility
Explore institution-curated learning material, approachable explanations, alternative input, and continuity between sessions. Work with educators and accessibility teams to define useful, measurable learning experiences.
Energy & environmental work
Investigate reference, documentation, and interpretation workflows close to where information is collected. Evaluate the computing resources and operational requirements of each defined use case.
Healthcare organizations
Explore staff-reviewed reference and documentation workflows with healthcare partners. Start with clearly scoped organizational tasks and the information, review, and deployment requirements surrounding them.
Professional & organizational work
Develop project-based workflows for research, document preparation, and internal knowledge. Define access, review, and output requirements around the team’s actual working environment.
How the roadmap progresses
A sequence of
meaningful milestones.
Different programmes move at different speeds. Product releases, partner deployments, and infrastructure each advance through the work needed for their next stage.
- Stage 01
Define the work.
Choose the user, the task, the operating environment, and the outcome that would make the project useful.
- Stage 02
Build & measure.
Create a focused implementation and examine capability, interaction, reliability, and resource use against that task.
- Stage 03
Evaluate in context.
Bring the work into a defined pilot or release review. Use findings from real workflows to refine the next version.
- Stage 04
Deliver & support.
Bring together the product, documentation, distribution, operations, and support needed for an ongoing customer experience.
What carries through every roadmap
A consistent standard
as the work expands.
Growth should make the experience more useful and understandable. These priorities guide the connections between our products, research, and future services.
Human direction
Keep permissions, proposed actions, and important decisions visible to the person responsible for the work.
Practical continuity
Bring the relevant project context forward while giving users clear control over what the workspace can access.
Evidence that helps development
Use repeatable tasks, observable results, and feedback from intended users to decide what to improve next.
A complete customer experience
Develop installation, learning, licensing, updates, and support alongside the features people come to use.
Understanding the direction
A few useful distinctions.
How do Aletheia and Heinrich fit together?
Aletheia is the EMPHOS language model. Heinrich is the workspace built around it, connecting conversations, project context, tools, approvals, and results. Their development is closely related, with model work and application work serving different parts of the experience.
Is Heinrich mobile part of the same direction?
Yes. The Heinrich mobile app is planned as an extension of the workspace, focused on project updates, conversations, review, and decisions away from the desktop.
Where does FieldLine PDF belong?
FieldLine PDF is our professional PDF product for Windows. It has a separate commercial roadmap centred on document work, the customer trial and purchase journey, licensing, and support. Its desktop app includes local FLORA.
Where do Planner, Construction, and RightNow belong?
FieldLine Planner, FieldLine Construction, and RightNow Maintenance are separate desktop products. Each Windows app includes local FLORA. Construction and RightNow browser and mobile apps do not. RightNow FLORA answers from the installed manual and does not read company maintenance records.
How will release information be shared?
Product pages will carry release details as each programme reaches its delivery milestones. This page brings the wider development priorities and longer-term research directions together in one place.
How can an organization get involved?
Start with the workflow or research question you want to explore. A useful first conversation identifies the intended users, environment, required inputs, and an outcome that both sides can evaluate.
Build the next chapter
Bring a useful question.
Start a focused conversation.
Research collaboration
Discuss model evaluation, runtime engineering, accessibility, or a focused application study.
Discuss research →Product & integration partners
Explore a deployment, licensing fit, or product workflow with clear goals and technical requirements.
Explore a partnership →Investors & strategic partners
Discuss the company’s development direction and request the appropriate investor or diligence material.
Contact investor relations →