Insights by OmkarStudio
Sign inGet started

Studio · Pipeline

What's on the workbench.

Where journal looks back, this page looks forward. Honest about scope: the things deliberately not on the bench are listed too.

Now shipping

The current focus.

Ecosystem rollout. Studio is at v1.0; the five sibling repos (consumer, netra, kriya, urja, admin) need to flip their auth CTAs to studio and adopt the shared footer pattern. Once that lands, the unified-account thesis is fully proven end-to-end.

  • Consumer auth migration — five `/auth/*` pages become redirects to studio
  • Sibling brand parity — favicon + logo + footer pattern + ™ contract
  • Kriya rename across siblings — `Astrology API` → `Kriya` in user-facing strings
  • Real-user traffic through studio's sign-in flow

Next up

On the dock.

Things with a clear shape that get built once the current rollout stabilises.

  • Theme toggle — light palette at urja first, then studio rewrites the atmospheric overrides for both modes
  • Cross-product data export — sibling endpoints fan out from studio, merge into one JSON
  • Sub-nav for `/account/*` — Stripe-style left rail across the eight account surfaces
  • Workbench evidence panel expansion — more signals, denser update cadence
  • Staff-auth role claim — admin delegates to studio with an `is_staff` flag

Backlog

Someday, maybe.

Real ideas with no current commitment. They might happen, they might not.

  • Newsletter / follow-the-studio signup separate from product accounts
  • Public roadmap voting (with friction — opinions are cheap)
  • An `/atelier` page rendering today's `studio_activity` as a live wall
  • Multi-language manifesto (Hindi first)
  • Open API for third-party integrations into the post-signin webhook channel

Deferred

Deliberate non-goals.

Decisions, not deferrals. The studio has chosen not to do these so it can do the things on the bench better.

  • Mobile app — web-first, indefinitely. The browser is the surface.
  • Multi-tenant org accounts — single-user model. No teams, no seats, no admin-of-admins.
  • White-label / reseller program — the brand IS the product.
  • Vendor SDK glue — every product depends only on siblings inside the family.
  • External icon kits, animation libraries, UI kits — all home-grown via urja.

Updated by hand, not generated. When something graduates from one section to another, the move shows up in /journal with the version it shipped in.