The integrity policy.

IP protection — the layered model

Local code can be reverse-engineered by determined adversaries. We make it expensive, not impossible. The real moat is velocity — we ship monthly, and a clone of Memagen™ made today is a snapshot of last month's product.

That said, here is what's in place for Pro Memagen™ Local:

1. Layer 1 — Legal. Memagen™ is a common-law trademark in active use. The Pro distribution ships with an EULA that prohibits reverse-engineering, redistribution, and derivative works. Each license is keyed to a buyer; pirated copies carry a per-license watermark that traces back to the original buyer. DMCA agent registered.
2. Layer 2 — Technical. Proprietary modules — the compound-graph engine, dream agents, code intelligence, cognition modules, sandboxed self-modification — are compiled to platform-specific binaries via Cython and stripped of symbols. The Python source is not distributed. Reverse-engineering effort goes from "open the .py" to "decompile a stripped C extension" — 50-100x harder.
3. Layer 3 — Architectural. The most valuable features — cloud-evolved schema, hosted dream consolidation, multi-agent orchestration at scale, the marketplace — are deferred to Pro Memagen™ Connected, which runs on our servers and is impossible to extract by definition. Local users get the single-machine version of the platform; Connected users get the features that fundamentally require the cloud.
4. Layer 4 — Velocity. We ship updates monthly. The changelog is public; the roadmap is public. A clone that captures Memagen™ today is a snapshot of an old version next month. The gap is the moat.
5. Layer 5 — Brand. Memagen™ is the brand. Forks of the V1-lite open-core code under MIT are welcome and lawful. They cannot use the Memagen™ name for the resulting product. The community recognizes the official build as the trust signal.

Fairness — the $50/year invisible budget

Every Memagen™ account has a $50/year invisible fairness budget. Refunds, credits, concessions, free upgrades, and exception requests all draw from it. 99% of accounts will never approach the limit. For the rest, a human reviews. We don't say no by default — we look at the case.

You don't see the budget. You see the answer. The budget exists to prevent us — a tiny team — from being bled dry by outliers, while defaulting to generous behavior with everyone else.

If you ever feel like Memagen™ has been unfair, email hello@memagen.com. We read every message. The fairness budget exists because we want to say yes by default.

Security disclosure

Report vulnerabilities to security@memagen.com. See /.well-known/security.txt for the canonical policy (RFC 9116).

We treat security reports as a priority. We will acknowledge receipt within 48 hours and, in good faith, work with you to fix and disclose responsibly.

Your data

Pro Memagen™ Local stores all data on your machine. It does not phone home except for license activation (once on first launch) and re-validation every 90 days. Re-validation transmits your license key and a machine fingerprint hash. Nothing else. No telemetry. No usage tracking. No analytics on your agent runs.

Pro Memagen™ Connected (when it launches) will follow the same principle: no data leaves your installation without explicit opt-in, and any cross-customer learning happens on aggregated, anonymized signal that cannot be reversed to identify a user.

Forks of the open-core

Memagen™ Lite is MIT-licensed. You may fork it, modify it, redistribute it, and even sell derivative works. You may not use the Memagen™ name for the resulting product, and you may not include the proprietary modules in any derivative without a separate commercial license. Press, reviews, comparison content, and academic citation are nominative fair use and welcomed.

When something goes wrong

Email hello@memagen.com. The founder reads it. The fairness budget covers most things. The integrity policy is the document you can hold us to.

— Tab Levitas, founder Last updated 2026-05-08