Skip to content

Changelog

Last updated 2 October 2026

What shipped, what is next, and what we are deliberately holding back.

v0.1.0

Phase 1 — Foundation

shipped2 October 2026
  • Next.js 15 App Router foundation with host-based subdomain routing for studio. and admin.
  • Neon PostgreSQL schema via Drizzle ORM: users, ai_models, generations, credit_transactions.
  • Admin-controlled engine registry — display names, provider routing, pricing and availability all live in the database.
  • BYOK security isolation: AES-256-GCM key encryption, and key inputs that render only for pass holders.
  • Prompt moderation pre-flight: artist references rewritten into musical descriptions before dispatch.
  • Provider engine shells for Gemini Lyria and ElevenLabs Music, sharing one normalised result shape.
  • Premium dark-mode marketing site, pricing grid and studio shell with a DAW-style layout.
v0.2.0

Phase 2 — Live generation

in progressPlanned
  • POST /api/generate with credit reservation and QStash enqueue.
  • Signature-verified generation worker calling Lyria and Eleven Music.
  • Mastering pass producing WAV and MP3, uploaded to blob storage.
  • Whop webhooks driving subscription tier, credit grants and BYOK pass state.
  • Webhook idempotency ledger for safe replays.
  • Rate limiting via Upstash Redis.
v0.3.0

Phase 3 — Public launch

plannedPlanned
  • Interactive waveform editing and region regeneration.
  • Public profile pages, track pages and dynamic OG image generation.
  • Checkout embed and self-serve plan management.
  • Stem export.
v1.0.0

Phase 4 — Scale and compliance

plannedPlanned
  • Similarity and originality auditing pipeline.
  • Per-provider cost telemetry and unit-economics dashboards.
  • Full audit log, GDPR export and delete workflows.

1.Versioning

We follow semantic versioning. Major versions are breaking changes to the public API, minor versions are new user-facing capability, and patch versions are fixes. The changelog is the canonical record — we do not publish a separate release feed.

2.Deprecations

When an underlying provider retires a model, the branded engine that used it is either repointed to a successor or deactivated from the admin registry. Deactivations are announced in-product at least 30 days in advance for paid tiers, and affected credits are never forfeited.