About

Who builds it

Sathi Systems builds and operates Sathi. Based in Japan, with engineering in Kathmandu, Nepal, the team is developing a connected ecosystem for home, work and everyday life. See the company profile. Altruistic is a working scratchpad on intelligence, cooperation and systems. Some ideas are tested in Sathi; the research extends beyond the product.

Where Sathi is today

• Stage: beta. One production deployment; its first ring of real users — the builder's own family — in daily use, in Nepali, English, Japanese, and Hindi.
• Signups: enabled at the public feature endpoint on 2026-09-20 for testing and feedback; the live signup screen follows the runtime gate, which can change.
• Guest chat: open to everyone, no account; nothing becomes memory, and guest conversations are kept for testing and feedback for as long as an operator setting allows (30 days by default).
• Pricing: no live billing; current beta access is free. Future hosted plans will publish finite cloud allowances before anyone pays.
• Hardware: a home speaker on open hardware is experimental; nothing is manufactured or sold.

What works, what is experimental, and what is only a plan — capability by capability — is on /explore.

Who owns what

Your records and personal understanding belong to you. Sharing with a family or organization follows the permissions you grant. You can export your archive or request deletion of live data, with signed operation receipts and separate backup-retention limits.* Sathi Systems owns and maintains the product software.

How Sathi sustains itself

Sathi has no advertising or engagement optimization, and personal data is never sold. Access is free during the current beta. Future hosted plans will publish prices and usage allowances before billing begins.

Sathi Systems offers transcription beta access and scopes AI integration pilots with organizations. Engagements and current availability are described on sathi.systems. Hardware remains experimental; dedicated and independently operated deployments are planned. Simplified Solutions (UK) is the current security partner; that relationship is not an independent audit of Sathi. Other referral partnerships are not signed. Future personal plans will distinguish finite hosted usage from processing on supported personal hardware.

Is Sathi open source?

The architecture is still being learned: Altruistic publishes the thinking, but the framework and reusable code are not released today. They will be distilled, generalized, and opened only after Sathi reaches saturation and survives repeated frontier-system, human, and security review. The openness guaranteed now and permanently is the one that protects you: your archive exports as signed, self-describing, readable files; paired devices are repointable; nothing about your exit depends on our permission.* More may open over time — decided deliberately, not by drift.

If Sathi disappears

Continuity is a product requirement, not an afterthought: the system is built to survive its own company.* Today your portable, signed archive remains readable and your paired devices can be repointed. Automatic one-step recreation of a complete Sathi on new infrastructure is a requirement we are working toward, not a shipped claim. The full answer lives on /trust.

What we publish, and what we don't

The rule: Clear information about your rights, available capabilities and how the system handles your data.

• Published: the principles, the promises, the authority ladder, the data boundary and the providers the code and our deployment records name (an inventory read from the running service is still to come), the memory semantics, the capability inventory with honest statuses, the threat posture and its limits, and everything you can inspect, export, or delete.
• Not published: retrieval and ranking internals, prompts, optimization details, deployment automation, hardware designs, unreleased products, and exact roadmap sequencing. These choices can affect privacy, retrieval, refusal and practical control. Their effects and limits must remain inspectable even where the implementation is private.