00 — Vision

YOU are the platform. (And if you want, you can be on the dev team too.)

BKA is an open-source AI-native creator OS that lets a creator own their audience, their domain, their content, and their infrastructure — without becoming a platform themselves. We don't host anything. That's the entire point.

Why this exists

The deal social platforms offered creators was simple: bring an audience, get reach. The deal got worse every year. Reach was throttled. Algorithms changed. Accounts got banned without recourse. Monetization got clawed back. The audience the creator brought to the platform stopped belonging to the creator.

Meanwhile the open web — your domain, your RSS feed, your email list, your subscribers — never went away. It just got hard enough to set up that most creators gave up and rented their audience from somebody else.

BKA is the hacker-era answer: open the app, follow a guided one-time setup, walk away with a real creator site on your own GitHub + your own Cloudflare account, with subscribers and comments and one-click syndication to whichever platforms you still want to use. No middleman. No hosted version. No us in the request path.

What it is

• A browser-first authoring app built on the 4G Web Dev Stack — Chat-style composer + media library + publish flow. Optional Tauri shell later for offline-first authoring.
• A two-repo content model — private repo is your working DB (drafts, scratch, history); public repo is your curated published surface. Publish action graduates an artifact from private → public.
• An automated deploy pipeline — push to public repo triggers Cloudflare Pages build, your site updates. CI/CD wired once, frictionless thereafter.
• A federated discovery layer — tiny optional indexer worker crawls registered creators' public feeds, BabyAI routes "what should I see next" queries. Metadata only, never content. Creators stay in control of what's discoverable.
• A Google SSO identity layer shared with the rest of the binary-blender app stack — same identity in BKA, Foundry, Community.

What it is NOT

• Not a hosted service. There is no bka.app/yourname. If we ran your site, we'd have your audience back on a platform — that's the trap we're avoiding.
• Not a SaaS. You pay GitHub and Cloudflare directly. Both free tiers cover a typical creator for a long time.
• Not a centralized social network. No algorithmic feed lives on our servers, because we don't have servers in the read path.
• Not part of the NovaSyn suite. NovaSyn is the desktop OS thesis; BKA is its own thing with its own brand.
• Not selling anything. No ads, no upsells, no telemetry, no premium tier.

Why teach the hard part instead of hiding it

The "set up your own Cloudflare account" step is real friction. We could remove it by hosting things ourselves. We won't, because:

1. If we run any infrastructure, we eventually become the platform we set out to replace.
2. Creators who learn how their site works can fix it, extend it, and leave us at any time. That's the point.
3. The audience self-selects. People who hear "you'll learn to set up Cloudflare in 15 minutes" and walk away were never going to own a platform anyway.

The wizard is a feature, not a workaround. It's the difference between renting and owning. The automation we DO build (publish CI/CD, feed generation, theme rendering, indexer integration) reduces the ongoing operational cost to near-zero. Setup is the only hard part, and it's hard exactly once.

The audience

The creator who:

• Has an audience or wants one
• Has a website or wants one
• Distrusts the platform deal, or has been burned by it
• Is willing to spend 15-30 minutes once to own their infrastructure
• Doesn't want to learn Wordpress, Astro, Vite, or any other stack-specific knowledge — just wants to make stuff and ship it

Not the audience: creators looking for a hosted SaaS. Those aren't on this branch; they should use Substack or Beehiiv or any of the existing platforms.

The compounding insight

Each piece of the BKA stack — per-creator GitHub repo, per-creator CF deploy, Google SSO across apps, indexer-as-metadata-only — was proven in the binary-blender app stack first (agicore-foundry, andon-loop-demo, community). BKA is the synthesis of patterns that already work, applied to a new use case. We're not inventing infrastructure; we're composing what's already shipped.

This is why it's the best app yet (per Christopher): all the pieces are real. The integration is the only new work.

Slogan

YOU are the platform.

That's the t-shirt. That's the README banner. That's the tagline on every social post.

The corollary: if anyone else can take it away, it isn't yours. BKA is the path back to owning it.