Service Boundaries

Each service in Upblit has a clear ownership boundary. Crossing these boundaries creates hidden coupling and makes the system harder to change.

Backend API

Owns: All business logic, authentication, telemetry ingest/query, AI Gateway, email coordination, file storage coordination.

Must not:

• Store files on local disk (use Supabase)
• Send emails directly (delegate to the email service)
• Expose raw stack traces in API responses

Frontend

Owns: All user-facing UI, dashboard, authentication flow, client-side state.

Must not:

• Call fetch() directly in components — use src/lib/api.ts
• Store API keys in localStorage or sessionStorage
• Implement business logic (delegate to backend)

Email Service

Owns: Email template rendering, delivery via Resend, webhook handling via Svix.

Must not:

• Access the database directly
• Handle user authentication

SDKs (Express / Go / Python)

Owns: HTTP request instrumentation, trace/log buffering and flushing, span context propagation.

Must not:

• Access the database directly
• Modify the HTTP request or response beyond trace context
• Throw errors that crash the instrumented application
• Read environment variables (accept config via constructor)

DeployX CLI

Owns: Git-based deployment workflow automation.

Must not:

• Store credentials
• Require external dependencies beyond Go stdlib

Boundary Violations to Watch For