Public technical overview

How Sonica is structured

This overview explains the platform at a useful architectural level while intentionally excluding credentials, private endpoints, database procedures, provider account handling, and anti-abuse implementation details.

Platform components

Product interfaces

The web experience, authenticated library, share pages, and server-side API clients submit requests through supported public interfaces.

Application services

Sonica validates requests, authorizes access, coordinates asynchronous generation, and exposes stable public status models.

Generation services

Specialized music-generation infrastructure transforms creative direction into audio and associated metadata.

Data and media

Account, credit, job, and track records support user libraries, status history, and controlled media access.

Generation flow

1Submit creative direction

2Validate and reserve credit

3Generate asynchronously

4Publish status and result

5Save, share, or download

Generation is asynchronous so clients can receive an accepted response quickly and track work without holding a long-running request open.

Credit model

Credits provide a predictable unit for generation. A request reserves its estimated cost while processing, captures it after successful completion, and restores it automatically when generation fails.

Purchased-credit provenance is tracked separately from free or promotional use where commercial-license eligibility depends on payment status.

Security and privacy principles

Authentication and ownership checks are enforced at protected resource boundaries.
API keys remain server-side and are never intended for public client code.
Public verification exposes only the metadata needed to confirm a license.
Private account data, prompts, and operational credentials are excluded from public certificates.
Rate limits, moderation, and request validation protect users and service reliability.
Internal topology and recovery procedures are deliberately not published.

Public interfaces

Sonica supports the web product, public song sharing, commercial-license verification, and the documented API v1. Integrations should use only documented public routes and should not depend on implementation details or undocumented behavior.