The investment thesis, November 2026

Intelligence needs a life to work with.

Other AI apps connect apps to their assistant. Akashic connects a person’s whole life into a record they own, then lets any assistant work with it.

Akashic must earn its place by making that foundation work every day. This is an early household pilot, not evidence of product-market fit or scalable economics.

Own the record. Upgrade the processor.

Akashic is permanent storage plus an organising system. The model is the processor working on it.

The foundation captures permitted signals, preserves evidence, and connects people, life areas, time, geography and matters. Compatible models and applications use the relevant context to analyse, create and act within their authority.

Changing the model should not mean rebuilding your history. Local inference may be part of that future where the model, hardware and task suit it; 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.

An appointment shows it.

Booking a child’s dentist needs the insurance policy, the clinic history, two calendars and the family’s places. Today those sit in separate places.

Context is scattered

A policy is in an inbox, a payment in a statement, a renewal in a calendar. Useful work means reconciling them and keeping them current.

Memory needs structure

An assistant needs to know whose document it is, when it applied, what replaced it and which source supports a claim.

Actions need continuity

An appointment or a renewal means tracking commitments, replies, permissions and outcomes across days and channels.

AI providers already offer memory, connectors and agents. Our thesis is that a user-owned foundation can support these across providers and applications, with continuity beyond any one interface.

One foundation. Many useful businesses on top.

The household operating layer

A child’s hospital appointment, historical blood results, and the Spanish needed for the visit. One person, history and calendar supports the whole chain.

Personal health context

Meal photos and estimated nutrients, activity, wearable trends and clinical records over time, with uncertainty and source evidence preserved.

Financial administration

Policy history and renewal dates for insurance comparison and negotiation; personal and company tax evidence assembled for review.

Specialist work and mini apps

Sources, experiments and decisions accumulate. Personal tools reuse that context, from a renovation tracker to a tutor tailored to next week.

These describe the direction. They are not claims that the complete workflows are delivered today.

The user owns the asset. We earn the relationship.

The user’s accumulated history is valuable to the user. It is not a data moat Akashic should hold hostage.

Our potential advantage is the 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.

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 shown through execution, retention, distribution and service quality. It is not established by declaring incumbents unable to compete.

A working foundation in an early pilot.

AreaCurrent basisNext proof
Daily useFounder use and an early household pilot; browser workbench and Android capture.Repeatable onboarding and sustained usefulness beyond the founder.
Connected recordDocument and message ingestion, structured knowledge, search, agenda and source-specific capture.Reliable coverage, freshness and identity across more sources. Capture gaps remain.
Replaceable AIModel and harness integrations working against a shared record.Measured task quality and context continuity across providers; qualify local tasks.
Useful workflowsAssistant, calendar and tracked work surfaces; explicit authorisation for external actions.Repeatable completion of the scenarios above, with bounded delegation and recovery from failure.
ExitA versioned export mechanism with a manifest and integrity hashes.Independent completeness, restoration and useful migration tests. An archive alone does not prove portability.

Build on standards. Prove the checkout.

Our direction is a documented, testable export profile that preserves originals, identities, relationships, timestamps, provenance and permissions, so another implementation can 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 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.

Start with the household. Earn expansion.

The first wedge

People coordinating a busy household: messages, appointments, documents, recurring administration and shared plans.

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.

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 shows development is real; it is not yet evidence of product-market fit or scalable unit economics.

Built around a real life. Designed to belong to yours.

Akashic is founded by Ehsan Ahmed, who goes by East. It 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.