Skip to main content
Oculon is organized so you can move from source data to decision-ready reporting without rebuilding the same logic in multiple places. The main structure is workspace-level, and each layer has a clear purpose.

​
The main layers

  • Workspace: your top-level environment for people, permissions, and settings.
  • Teamspaces or shared areas: Collaboration zones for teams or projects.
  • Models: where planning logic, variables, dimensions, and formulas live.
  • Databases: where imported or managed records are stored.
  • Views: filtered, saved ways to look at model or database content.
  • Boards: presentation surfaces for charts, tables, and KPI blocks.

​
How data moves through the product

Data usually enters Oculon through integrations or databases. Models use that data to calculate metrics and forecasts. Views narrow a model or database to the right slice of information. Boards package the result or embed the right view so stakeholders can review it quickly.

​
Where collaboration happens

Collaboration happens at several levels:
  • Workspace admins manage access and security.
  • Model builders own structure and formulas.
  • Collaborators review scenarios, comments, views, and boards.
  • Teams share only the level of detail each audience needs.

​
A practical way to think about the product

  • If you are building logic, work in a model.
  • If you are shaping a dataset, work in a database.
  • If you are narrowing content from a model or database, use a view.
  • If you are presenting insights, use a board.