The household operating layer
Coordinate a child’s hospital appointment, prepare historical blood results and practise the Spanish needed for the visit. The same person, history and calendar support the whole chain.
For investors / September 2026
The lasting foundation for a changing AI world.
Akashic organises a person’s digital life into a record they own. Replaceable AI turns that growing context into useful work.
The investment thesis: as intelligence improves, a reliable, permissioned and portable personal data foundation becomes more useful. The business must earn its place by making that foundation work every day.
The product
Own the record.
Upgrade the processor.
Think of Akashic as permanent storage plus an organising system. The LLM is the processor working on it.
The foundation captures permitted signals, preserves evidence, and connects people, domains, time, geography and projects. Compatible models and applications use the relevant context to analyse, create and act within their authority.
Changing the processor should not mean losing the files. Changing the model should not mean rebuilding your history. Local inference can be part of that future where the model, hardware and task are suitable; a fully local replacement for every workflow is not a current promise.
Inputs
Digital signals
Communications, documents, photos, health, location, calendars and external information.
Lasting asset
The user’s record
Identity, relationships, history, preferences, provenance and permissions.
Replaceable capability
Models & applications
Better reasoning, new workflows and personal tools built on existing context.
Why this matters
Intelligence needs a life to work with.
Context is scattered
A policy is in an inbox, a payment in a statement, a renewal in a calendar. Useful work depends on reconciling these pieces and keeping them current.
Memory needs structure
Retrieving a document is only the beginning. An assistant needs to know whose document it is, when it applied, what replaced it and which source supports a claim.
Actions need continuity
Booking an appointment or handling a renewal means tracking commitments, replies, permissions and outcomes across days and channels.
AI providers already offer memory, connectors and agents. Akashic’s thesis is that a user-owned foundation can support these capabilities across providers and applications, with continuity beyond any one interface.
The product opportunity
One foundation. Many useful businesses on top.
Personal health context
Connect meal photos and estimated nutrients to activity, wearable trends and clinical records over time. Preserve uncertainty and source evidence.
Financial administration
Use policy history and renewal dates for insurance comparison and negotiation; assemble personal and company tax evidence for review.
Specialist work and mini apps
Research and development accumulate sources, experiments and decisions. Personal tools reuse that context, from a renovation tracker to a tutor tailored to next week.
These connected experiences describe the direction. They are not claims that the complete workflows are delivered today.
Defensibility
The user owns the asset.
We earn the relationship.
The user’s accumulated history is valuable to the user. It is not a proprietary data moat that Akashic should hold hostage.
Our potential advantage is the accumulated work of making that record reliable and useful: integrations that survive change, accurate identity and time handling, traceable evidence, permission boundaries, dependable workflows and a product people trust with daily life.
Each successful use can give someone another reason to keep using Akashic. Reusable integrations and workflow knowledge can improve delivery for future users without pooling their private records.
Competitors can copy features and pursue the same architecture. Defensibility has to be demonstrated through execution, retention, distribution and service quality. It is not established by declaring incumbents unable to compete.
What exists / what must be proved
A working foundation in an early pilot.
| Area | Current basis | Next proof |
|---|---|---|
| Daily use | Founder use and an early household pilot; browser workbench and Android capture. | Repeatable onboarding and sustained usefulness beyond the founder. |
| Connected record | Document and message ingestion, structured knowledge, search, agenda and source-specific capture. | Reliable coverage, freshness and identity across more sources. Capture gaps remain. |
| Replaceable AI | Model and harness integrations working against a shared record. | Measured task quality and context continuity across providers; qualify local tasks. |
| Useful workflows | Assistant, calendar and tracked work surfaces; explicit authorisation for external actions. | Repeatable completion of the connected scenarios above, with bounded delegation and recovery from failure. |
| Exit | A versioned export mechanism with a manifest and integrity hashes. | Independent completeness, restoration and useful migration tests. An archive alone does not prove portability. |
An open foundation
Build on standards.
Prove the checkout.
Our direction is a documented, testable export profile that preserves originals, identities, relationships, timestamps, provenance and permissions. Another implementation should be able to make useful sense of it.
Relevant building blocks include JSON-LD for linked data, W3C PROV for provenance and RO-Crate for packaging. Solid and the Linked Web Storage draft are relevant to independently controlled storage and access.
These are standards and ecosystem directions to evaluate, not a claim of implemented conformance or certification. Where a personal-record profile is missing, we can publish one with validators and migration examples, and invite other implementations to use it. Adoption would make it a standard in practice; a name alone would not.
Commercial thesis
Start with the household. Earn expansion.
The first wedge
People coordinating a busy household: messages, appointments, documents, recurring administration and shared plans. Frequent, connected needs can demonstrate the foundation’s value.
What people would pay for
Reliable capture and organisation, a managed service, and useful work completed. Household subscriptions and specialised workflow offerings are hypotheses to test, not proven economics.
How it could grow
From individual to household, then to professional and specialist uses where the same context already helps. Shared access must preserve each person’s ownership and boundaries.
The next milestones
Make the thesis measurable.
- Onboard households without founder intervention, and measure repeat use and retention.
- Prove source coverage, freshness, provenance and meaningful export-and-restore.
- Complete a small set of useful workflows reliably; measure failures, user corrections and time saved.
- Demonstrate model switching against the same context with repeatable quality checks.
- Establish delivery costs, willingness to pay and support burden.
Security assurance, permission design, connector reliability, phone capture and operational recovery remain substantial work. The pilot is evidence that development is real; it is not yet evidence of product-market fit or scalable unit economics.
The founder
Built around a real life.
Designed to belong to yours.
Akashic is founded by Ehsan Ahmed, who goes by East. The product began with his own need for continuity across family, work, health and administration. We are looking for conversations with investors who understand patient infrastructure work and the value of user ownership.