01
A project with a home.
Connect a working folder to its chats, permissions, project memory, and outputs. Keep the material for a task together, from the first request to the files you keep.
Folders · context · project stateHEINRICHBY EMPHOS GROUP
AI workspace · Powered by Aletheia
Your ideas.
Work you can review.
Bring your projects, conversations, files, and tools into one continuing workspace. Heinrich connects Aletheia’s intelligence to the work you want to finish—with a plan, clear permissions, and results you can inspect.
Desktop development · Local project context · CPU inference
From request to result
- Choose the project.Connect the folder, context, and outcome.
- Review the plan.Understand the steps and required access.
- Follow the work.Tools, file changes, and output checks.
- Inspect the result.Usable files and a record of the actions.
AletheiaThe model behind the workspace
ProjectsFiles and context kept together
CPU inferenceModel execution on the computer
Proof receiptsActions connected to their results
Built around the project
A place to think.
A place to do the work.
A useful request usually belongs to something larger: a document, a codebase, a research question, or a project with another step still to come. Heinrich gives that work a home.
Start with your material.
Bind a project to its working folder. Keep relevant files, access permissions, and project memory connected to the conversations around the task.
Move from discussion into action.
Use a request to develop a plan, work with permitted tools, and produce files. Follow the progress and review decisions as the task develops.
Return with context.
Keep goals, checkpoints, action records, and saved outputs so the next session starts with the work already in view.
Core capabilities
Seven connected capabilities.
One working environment.
The model, the project, and the tools each have a clear role. Heinrich brings them together around the result you are trying to reach.
02
Conversation that stays connected.
Use natural language to plan, ask questions, build, and review within a project. Branch, archive, and export conversations as the work develops.
Discuss · refine · review03
Goals with a working plan.
Turn a larger request into steps, dependencies, and expected deliverables. Review the plan and required access before the workflow runs.
Plan · approve · execute04
Tools within reach.
Bring files, commands, a browser, and connected services into the task. Configured permissions define the tools and information available to each workflow.
Local tools · connections · permissions05
Files you can use.
Create documents, code, and structured data as project artifacts. Inspect the output and run the checks appropriate to the requested work.
Create · inspect · check06
A record behind the result.
Proof receipts connect actions to their outputs and supporting checks. Review what ran, inspect the files it produced, and see what remains open.
Actions · artifacts · proof receipts07
Progress that carries forward.
Keep goals, working memory, pending tasks, and checkpoints across sessions. Return to the project with the context needed to continue, and control sensitive actions through explicit approvals.
Save · resume · stay in controlAletheia at the core
Our language model.
Your working context.
Aletheia is the EMPHOS language model powering Heinrich. It processes language through a recurrent oscillator state that carries context forward. The desktop workspace connects that capability to files, plans, and tools.
01 / Intelligence
Aletheia
Language generation and context processing. Aletheia uses GPU training and CPU inference, with separate development and everyday execution paths.
02 / Action
Agent runtime
Plans, permissions, task execution, and output checks. The runtime connects a proposed step to the tools, files, and evidence required to carry it out.
03 / Continuity
Project state
Project folders, chats, memory, goals, checkpoints, proof records, and artifacts. The work retains a history you can return to across sessions.
04 / Interaction
Heinrich desktop
The interface for directing and reviewing the work: conversation, code and command workspaces, browser access, project settings, and review surfaces.
Local execution is part of the design. Aletheia’s inference path runs on the computer’s CPU. Project state and proof records stay with the local workspace, while connected services use the access configured for the task.
A practical way to work
Set the direction.
Stay connected to the result.
A continuing workflow keeps the outcome, the actions, and the review connected.
Define the outcome.
Choose the project and explain the result, constraints, and materials that matter.
Review the approach.
Inspect the plan, expected files, and requested access before approving the work.
Follow execution.
Track the steps, respond to approval requests, and inspect tool feedback and blockers.
Review and continue.
Open the generated files, check the action record, and continue with the next decision.
Work worth carrying forward
From a first question
to something you can use.
Heinrich is built for work where context, files, and follow-through matter together.
Build software from a request.
Turn the intended behaviour into a plan, make changes inside the project, and review the resulting code and checks.
Research with the sources in view.
Work through a defined question using permitted materials and connections. Keep the findings and source references alongside the draft.
Continue a longer project.
Return to saved goals, decisions, and open work. Use project memory and checkpoints to pick up the next step.
Prepare and review documents.
Develop a draft, organize its information, and save a usable document. Review the content and the generated file in the same workflow.
Run project checks.
Connect tests and validation commands to the task. Inspect failures, review changes, and keep a record of the outcome.
Develop a product idea.
Organize requirements, compare approaches, draft specifications, and maintain the questions that still need an answer.
Keep context between sessions.
Carry relevant project information and action records forward so work can continue over days instead of starting from an empty conversation.
Prepare material for a handoff.
Bring files, decisions, checks, and open items into a reviewable package for the people taking the work forward.
Deliverables in the project
Keep the file. Keep the work behind it.
Text and Markdown. Code and HTML. JSON and CSV. PDF and office documents. The workspace connects generated artifacts to the task and the checks performed on them.
You direct the work
Clear scope.
Visible actions.
Permissions, plan review, approvals, and proof records give you a way to understand what Heinrich can access and inspect what it has done.
Project boundaries
Connect the intended folder and define its access permissions. The working context stays tied to the task.
Plan review
Review a multi-step goal, its dependencies, and expected outputs before approving execution.
Sensitive actions
High-risk and destructive operations require explicit confirmation. You remain part of the decision.
File-change snapshots
Snapshots support the review and recovery of overwritten files as the project changes.
Persistent checkpoints
Saved goals and pending work support a workflow that can pause and resume across sessions.
Output inspection
Check the resulting artifacts and action records before carrying the work into its next stage.
Product development
A focused desktop workspace.
A wider direction.
Heinrich’s development connects the model, the application, and the environments where people want to use them.
Heinrich
Projects, chats, goals, local tools, and reviewable outputs. Discuss a demonstration around your own workflow and the next steps for early access.
Heinrich app
Continue selected conversations, check progress, review results, and make decisions away from the desk. The mobile direction extends continuity to a smaller screen.
Your environment
Explore organization-specific workflows, customer-controlled deployment, and future integrations through a defined technical scope.
Common questions
Get to know the workspace.
What is Heinrich?
Heinrich is EMPHOS’s desktop AI workspace, powered by Aletheia. It connects conversations with projects, local memory, plans, tools, generated files, and records of completed actions.
How are Heinrich and Aletheia different?
Aletheia is the language model. Heinrich is the application and agent runtime around it. The model processes language; the workspace connects that capability to the project, its tools, and the results you review.
Does Heinrich run locally?
The desktop architecture runs Aletheia inference on the computer’s CPU and keeps project state and proof records on the user’s machine. External services follow the connections and permissions configured for the task.
Does every action require approval?
Heinrich uses project permissions and approval-gated plans to define the work. Sensitive and destructive actions require explicit confirmation. The applicable permissions and risk of the action determine where approval is needed.
What kinds of files can Heinrich create?
The workspace supports text, Markdown, code, HTML, JSON, CSV, PDF, and office-document artifacts. The available tools and task determine the output format and the checks performed on the resulting file.
Can I continue a task later?
Yes. Project memory, goals, pending work, checkpoints, and proof receipts persist across sessions so you can return to the project and continue its open work.
How can I arrange a demonstration?
Contact EMPHOS with the work you would like to explore, your computer or deployment environment, and the kinds of files and tools involved. We can discuss a demonstration and the appropriate route for early access.
Is there a Heinrich mobile app?
The mobile app is a separate development direction focused on continuing conversations, checking progress, reviewing results, and making decisions away from the desktop. Explore the Heinrich mobile app →
Start with a real project
Bring the work.
Explore Heinrich.
Tell EMPHOS what you want to build, research, or finish. We can discuss a demonstration, early access, or a focused integration conversation.