Loading page
One catalogue for the whole platform, filtered to what applies to ojas.events. The page also publishes what the software does not do yet, in full and without burying it.
15 capabilities
Buying and deploying a Blueprint works; publishing your own is still not a shipped path.
We saidLater · The Venture Blueprint — package a working events operation (playbook, catalogue, supply, brand) into a design you deploy in one purchase.
Ventures · blueprints
What a Blueprint deploysThe backend serves certificate routes for completed enrolments; no dedicated certificate screen is built yet, so this is API-only.
Learning · academy
Openings, applicants and applications are managed in the console, with interviews, scorecards, offers and talent pools served by the backend.
People and work · ats
Files are registered and linked to records through the backend and hooks; no file-manager screen of its own is built yet.
Platform · attachments
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
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
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
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
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
Return requests, return lines and replacements are available through the API only; no hook or screen consumes them yet.
Commerce · returns
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
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
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
A nightly reconcile builds task flow and project health facts that feed dashboards and metrics; the package serves no route of its own.
People and work · work-analytics
Timesheets are managed from the console; the time-log routes behind them were not traced to a screen of their own.
People and work · worklog
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.