Pure-Client Products

How new AI products can start as frontend-first products.

“Pure-client product” does not mean “no backend at all.” It means you stop rebuilding the AI backend for every product.

Downcity lets a new product start from the frontend, extension, or app and connect to an already deployed Federation. You can validate the product UX first, then decide how much product-specific backend you really need.

Good fits

  • lightweight web tools
  • Chrome extensions
  • desktop shells
  • mobile entries
  • client demos
  • internal tools

The client owns:

  • UI and interaction
  • calling Federation User
  • storing or refreshing user_token

The Federation owns:

  • provider keys
  • model directory
  • user_token verification
  • service routing
  • usage records
  • hooks and billing logic

The most common minimum shape

City frontend
  ↓
Your login / token-issuing endpoint
  ↓
Federation

That product backend can stay very thin at first:

  • user login
  • requesting a User Token through Federation Admin
  • returning user_token to the client

User sessions own identity, permissions, and Credits. City automatically carries optional city_id for logs, usage, and job source only. Business calls use federation.user.service(name) on the current Federation; administrators use a separate Session.

Why this fits early products better

  • you stop copying provider integrations for every AI idea
  • the frontend can ship much earlier
  • multiple products share one AI calling, logging, and quota layer

If the product gets more complex later, then add more business backend. Do not duplicate the whole AI infrastructure on day one.