Vritto

Vritto is a private personal organizer for the parts of life that usually live scattered across separate apps: plans, people, health, money, travel, purchases, notes, memories, and more. Each area has a focused module, but the underlying record is shared, so information entered once can remain useful everywhere it matters.

I founded Vritto and lead its product, design, and engineering across the web platform, native iPhone and Android clients, backend systems, and AI layer.

The Product Bet

Most personal software understands only one slice of a person. A calendar knows time. A finance app knows transactions. A contact app knows names. A health app knows measurements. The relationships between those facts—and the work of coordinating them—remain in the user's head.

Flexible workspaces solve a different problem, but they often begin with a blank canvas. Users have to design databases, properties, views, and conventions before the system becomes useful. That flexibility creates its own maintenance burden and still leaves every category represented as a generic page.

Vritto takes a more opinionated approach: structure each area according to what it represents, then connect those areas through one private record. A subscription behaves like a subscription. A trip has legs, stays, places, and plans. A person can be connected to dinners, gifts, memories, and future commitments without being duplicated across them.

Connected by Design

Vritto's modules are purpose-built destinations rather than configurable databases. Each module owns the fields, views, actions, and summaries its subject needs, while shared contracts let the same person, place, asset, date, or financial fact participate in more than one context.

That distinction shapes the product in three ways:

• Focused on its own. Orders can model shipments, pickup windows, returns, refunds, merchants, and spending without forcing that structure onto unrelated records.
• More useful together. A dinner can connect a person, reservation, place, task, and planned spend. A trip can collect flights, stays, packing, dining, and memories around one experience.
• Readable without AI. Modules, dashboards, reports, and relationships remain useful on their own. Intelligence is a capability layered on top, not a dependency for understanding the user's data.

Orders — a purpose-built operational view, not a generic table

Movies — the same module system adapted to an entirely different kind of record

2 images

Intelligence with Boundaries

SahAI is the connective intelligence inside Vritto. It can answer questions across the records a user allows, prepare briefs, find relevant context, and propose changes for review. The goal is not to put a chatbot beside every screen; it is to make the record more useful while keeping the user in control of what the system can see and change.

The same permission model extends to external assistants through the Model Context Protocol. Access is granted per client and per module, with separate read and write levels. Sensitive areas can remain unavailable, permissions can be revoked, and proposed changes can pass through the same review surface as SahAI actions.

This creates a deliberate separation between the record and the intelligence. The data lives in Vritto. The user can choose whether intelligence comes from SahAI, an external assistant, or nowhere at all.

One Platform, Three Clients

Vritto is built as one product across web, iPhone, and Android rather than three disconnected implementations. Shared schemas and backend-owned actions define how records behave; each client then expresses those contracts using platform-native interaction patterns.

The web app is the richest management surface and the current reference implementation. The iPhone client is being built in SwiftUI and the Android client in Jetpack Compose, with native navigation, capture, notifications, offline behavior, and device integrations treated as product capabilities—not wrappers around the website.

The platform is intentionally pre-launch. Native parity, onboarding, billing, external integrations, security verification, and beta operations are being completed before the product is opened broadly.

From Project to Company

Vritto began as software I wanted for myself: one trustworthy place for a life spread across too many applications. Building the first modules exposed a larger product opportunity. The difficult part was not adding more categories; it was defining a system that could hold very different kinds of information without flattening them into generic records or turning the interface into a maze.

That work evolved into Vritto, Inc., founded in 2026. The company is being built around a straightforward promise: make useful subscription software, keep incentives aligned with the people using it, and treat privacy and user control as product architecture rather than policy-page language.

The official Vritto website owns the customer-facing product story. This page documents the founder and product-building story behind it.

Current Stage

Working today: the web product, a broad catalog of structured modules, shared contracts, cross-module relationships, dashboards, notifications, SahAI surfaces, reviewable AI actions, and the MCP permission plane.

In active development: native-client hardening, onboarding, billing and entitlements, external capture and synchronization, launch operations, and the final trust and compliance work required for broader access.

Deliberately not claimed yet: public availability, complete native parity, or a finished product. Vritto is substantial and actively used, but the current phase is about turning that breadth into a dependable launch experience.

My Role

As founder, I set the product thesis, define scope and sequencing, design the experience, and build the system across clients and backend services. That includes choosing where the product should be opinionated, establishing shared contracts, designing permission boundaries, deciding what belongs in the launch, and doing the engineering work required to make those decisions real.

Vritto has become my largest exercise in product judgment. Its complexity does not come from one technically difficult feature. It comes from creating coherence across dozens of domains while resisting the temptation to treat breadth as progress by itself.

The work now is the transition from an ambitious system to a trustworthy company and product: narrower promises, clearer evidence, honest stage-setting, and a launch that earns the responsibility of holding the private details of a life.