Made Open

Product Overview: What Made Open Is (and Is NOT)

What It Is

Made Open is a self-hosted personal data platform that:

  1. Centralizes your data — contacts, calls, SMS, email, calendar, location, files, health, finance — into a unified knowledge graph you control
  2. Runs on your infrastructure — your laptop, a home server, a VPS, or a hosted zero-knowledge instance
  3. Connects existing services via plugins — you bring your Twilio account, your Microsoft 365 login, your Google OAuth. Your keys, your data.
  4. Enables cross-data intelligence — a Rules Engine fires based on compound conditions across data domains (location + caller identity + calendar = intelligent call routing). AI has deep context because the data is already unified and indexed.
  5. Exposes native apps — web, Android, and Windows clients that are full communication + data management interfaces, not just dashboards

The Design Law

Every integration must first land as data in the unified model, not as a new action. Actions are consumers of data, never the source of truth.

A Microsoft Graph connector doesn't fetch your calendar at query time — it syncs your calendar into your database so it's always current and queryable without latency or API limits. Twilio doesn't look up call history on demand — every call is stored as a Message entity the moment it happens.

This law is enforced architecturally. New connectors add data. Rules and AI consume data. Nothing bypasses the data layer.

Who It's For

  • Privacy-conscious individuals who want to stop fragmenting their digital life across corporate services
  • Technical founders and engineers who understand that data ownership is an infrastructure problem, not an app problem
  • Power users who want cross-service automation that isn't possible when your data is siloed
  • "Made Open" builders who want to create services that compete on trust and data sovereignty rather than data extraction

Non-Goals

  • Not a hosted SaaS where we hold your data. The entire point is that you hold your data.
  • Not "yet another AI assistant wrapper." The AI is one application on top of the data layer. If you turn the AI off, the platform still works: it's a communication hub, an automation engine, and a personal data warehouse.
  • Not a PIM app. This is an infrastructure layer, not a pretty contacts app. (Though the apps on top of it are pretty.)
  • Not dependent on AI for basic operations. Call routing, DND rules, contact sync — none of these require LLM involvement. Rules run on the data directly. AI is for complex reasoning.
  • Not a replacement for your phone carrier. Twilio is the voice/SMS layer; you bring your own account and number.

The Flagship Capability

The clearest demonstration of why this architecture wins:

Intelligent Call Router — when your partner calls while you're at work:

  • System knows caller identity (from contacts)
  • System knows your location (from Android GPS, streaming in background)
  • System knows your schedule (from MS Graph calendar)
  • Rule fires: SMS your partner with the office number so they can call the store
  • Total latency: < 2 seconds. No AI involved. Just a database query and a rule evaluation.

In OpenClaw, this requires 10 sequential LLM tool calls, 10–30 second latency, and costs LLM API tokens. Here it's a single database lookup.

Platform Layers (Top to Bottom)

LayerWhat's Here
ApplicationsAI assistant, CRM, CMS, custom third-party apps
PresentationWeb app, Android app, Windows agent, conversational interfaces
Data AccessSovereign API — authenticated, access-controlled, fully audited
IntelligenceRules Engine (event-driven automation), AI Service (RAG + LLM routing)
ProcessingETL pipelines, entity recognition, relationship inference, search indexing
StorageKnowledge graph (PostgreSQL), search index (Meilisearch), event store (NATS), state (Redis)
IntegrationConnector plugins (MS Graph, Twilio, Google, etc.)
IdentityCredential Wallet, Capability Registry, Policy Service, Audit Log

Deployment Models

ModelWhoNotes
Self-hostedTechnical usersFull control, runs on your hardware
Managed self-hostingUsers who want control without opsDeploy to your own VPS via Docker Compose
Hosted (zero-knowledge)Non-technical usersProvider hosts, but your data is end-to-end encrypted with keys only you hold