The platform is public. The engineering is the value.

We publish our tools. Three projects under github.com/Simple4uhq: the SAE4U Agent (the multi-tenant agent platform we built as a SaaS product, published when we stopped selling it in May 2026), sae4u-memory (full persistent memory architecture for Claude, a sister project), and SHAITS (a trust standard for self-hosted AI). MIT and Apache 2. Free to self-host.

Public repositories

Three projects, one philosophy.

Each one came out of building production AI infrastructure. Each one is yours to fork.

SAE4U Agent · Apache 2

Multi-tenant AI agent platform

The orchestrator and per-tenant runtime template we built for our SaaS, published as a snapshot in May 2026.

FastAPI control plane on dedicated ops-master, per-tenant DigitalOcean droplets via DO API + cloud-init, Fernet-encrypted bot pool, Telegram-first agent runtime with FTS5 + sqlite-vec hybrid knowledge base. Includes ARCHITECTURE.md narrative documenting what we built, what we learned, and why we walked away from selling it as SaaS.

Python · FastAPI · SQLite · Apache 2 · self-hostable
View on GitHub → Hire us to run it →
sae4u-memory · MIT · v0.2.0

Persistent memory architecture for Claude

Not just an MCP server: the full memory pattern, hooks, rules, prompts, templates, and a customizable peer-coder persona.

MCP server with two-corpus recall (SQLite facts + markdown files in your auto-memory dirs). Plus the architecture we run in production: a 10-min UserPromptSubmit hook that forces brief memory reviews, 10 universal feedback rules (no session-state confabulation, mirror-handoff, no-hardcode, post-write review, …), session-open and session-close prompts paired with the rules, a MEMORY.md index format, and Simple: a generic peer-coder persona with persistent memory awareness. sae4u-memory init --code-full wires the whole pattern into Claude Code in one command. Sister project to SAE4U Agent.

Python · MCP · SQLite + FTS5 · hooks · rules · prompts · persona
View on GitHub → Install from PyPI →
SHAITS · Open spec

Self-Hosted AI Trust Standard

Open specification for trustworthy self-hosted AI agents. Our own self-audit is next on the registry.

A 125-point scoring framework for self-hosted AI: data residency, audit logging, telemetry policy, encryption at rest, key rotation, dependency provenance. Cloud-only products are out of scope by design. We will publish our own self-audit first. Other self-hosted projects encouraged to audit + register.

Open spec · markdown · self-audit framework
View on GitHub → Read the standard →
Open source vs retainer

Fork it, or have us build yours.

SAE4U Agent on GitHub is the architecture, with empty slots for the parts that make it actually useful for a specific business. Anyone can fork it and fill it themselves. Or we build a system for your business and run it on the retainer, with no extra AI line item.

Open source · self-host

Architecture with empty slots

The orchestrator, the runtime template, the knowledge base schema, the OAuth wiring, the prompt scaffolding: all there. The slots for what your business actually is (your tools, your team's voice, your workflows, your data) come empty. You fill them. You host them. You maintain them.

  • Apache 2 license, fork freely
  • You provision your own infrastructure
  • You wire your own OAuth integrations
  • You write the agent’s brief (its voice and rules) and workflows
  • You pay only your hosting and AI-provider bills
Fork on GitHub →
Retainer · we run it

Filled, deployed, operated

Inside a retainer, the system is yours alone: your tools wired, your voice in the agent’s brief, your workflows automated, your data flowing. You get a Telegram chat with an agent that already knows your operation, and we keep the engineering behind it sharp every week.

  • Included in the retainer, no separate AI line
  • We provision and run the infrastructure
  • We wire OAuth and connect every tool you use
  • We tune the agent’s brief, ship workflows, monitor health
  • You use the agent to track what and how
Discuss an engagement →
Why open source

No proprietary moat. The engineering is the moat.

Most AI consulting firms keep their tooling proprietary. We took the opposite stance. The reason: clients shouldn't be locked into our tools, they should pick us because the engineering is real, not because we hold their AI hostage. When you engage us, the code we write for you is yours: you can audit it and run it elsewhere if our engagement ever ends. Trust comes from full visibility, not from contractual lock-in.

Practically: this also doubles as our most credible lead-gen channel. Developers find the code, read the engineering, decide we're real, contact us. That's better signal than any landing page can produce alone.

Describe your business. Get the one-page plan.

It says what to build first, what it connects to, and the fixed price. Free, from the founder, within 48 hours.

Or book the call

Fifteen minutes, no deck. If we are not the right team, you will hear that on the call and get a name of who is.

Prefer to talk first: book a call with Slava Phone: (929) 640-6940 Email: office@simple4u.io Based in Brooklyn, NY. We work with clients anywhere; in New York we come to you.

Your message reaches the founder directly.