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.
9 capabilities
Live
- Live
Kanban boards over pipelines
A board shows records as cards in the columns of a pipeline, and cards are moved and ranked on the board.
Platform · boards
- Live
One activity feed per record
A record's activity and audit entries read from one feed, shown as the timeline panel on lead, account and project pages.
Platform · timeline
- Live
Saved views and column choices
People save filtered views of a list and choose which columns it shows.
Platform · views
- Live
Outbound webhooks and delivery log
Webhook endpoints are subscribed to events and each delivery attempt is listed in the console.
Platform · webhooks
- Live
Automations and run history
Automation rules with triggers, conditions and actions are built in the console and their runs are listed.
Platform · workflows
Live in part
- 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
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
Not started
- Not started
A track record
No outside institution is running on Ojas yet — you would be the first.
Platform · tenants
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.