What is live, and what is not
One catalogue for the whole platform, filtered to what applies to ojas.vc. The page also publishes what the software does not do yet, in full and without burying it.
12 capabilities
Live in part
- Live in part
Course certificates
The backend serves certificate routes for completed enrolments; no dedicated certificate screen is built yet, so this is API-only.
Learning · academy
- Live in part
Openings, applicants and applications
Openings, applicants and applications are managed in the console, with interviews, scorecards, offers and talent pools served by the backend.
People and work · ats
- Live in part
Files and attachment links
Files are registered and linked to records through the backend and hooks; no file-manager screen of its own is built yet.
Platform · attachments
- Live in part
Plans, invoices and commissions
Billing configuration, invoices and commission schedules are managed in the console; subscriptions, usage and settlements are served by the backend without a screen traced for each.
Money and books · billing
- Live in part
Entity classes, categories and custom attributes
The API defines entity classes, categories, custom attributes and relations that other modules reuse; the one screen using it today is entity search in pickers, with no screen for authoring definitions.
Platform · entities
- Live in part
Loyalty programs with a points ledger
The backend serves loyalty programs, member accounts and an append-only points ledger, but there is no screen or hook for it yet; it is API-only.
Commerce · loyalty
- Live in part
Bills of materials and production orders
The backend serves bills of materials and production orders and runs, but there is no screen or hook for it yet; it is API-only.
Places and assets · manufacturing
- Live in part
Lead-provider polling recovery
A scheduled sweep fetches Meta, Google and LinkedIn lead-form submissions missed while a webhook was down; it serves no routes and has no screen.
Sales and marketing · provider-sync
- Live in part
Return requests and replacements
Return requests, return lines and replacements are available through the API only; no hook or screen consumes them yet.
Commerce · returns
- Live in part
Subscription products and subscribers
Subscription products, public subscribe and gift routes, subscriber lists and invoices are served by the API; a subscriber-list container exists but no app route mounts it yet.
Commerce · subscriptions
- Live in part
Appearance and email change
The API lets a signed-in person set an appearance preference and change their email address by confirming a link; a hook exists for appearance, and no screen for either was found.
Identity and access · users
- Live in part
Vaastu calculation engine
A computation library measures plan geometry, zones, door positions, Ayadi, magnetic declination and room scores; it serves no routes itself and is reached through the Pujavani API.
Places and assets · vastu
How to read this page
Live means a route, a screen and the data behind it are all reachable today. Live in part says what is and is not covered. Coming soon only appears with the work package that owns it, and any quarter shown is a target, not a promise. Not started carries no date.
Where a row replaces a limit we once published, it quotes that limit as we wrote it and dates the day the capability became reachable.