What is a model?

Before diving into models, let’s quickly revisit what databases are for. Databases are where you store your raw data in Runway at various levels of granularity. This could include:

  • Data pulled directly from integrations.
  • Mapping tables you configure.
  • Highly dimensional assumptions you input manually.

Databases are powerful for modeling and transforming data at scale, but they’re not always ideal for presenting or interacting with that data in a visual or lightweight format.

That’s where models and pages come in:

  • Models are structured tables where each row represents a driver. You can include:
    • Drivers pulled from databases or other models.
    • New computed drivers created directly within the model to aggregate data or layer in assumptions.
  • Pages are flexible canvases where you can present your data using various block types:

So why use models instead of driver tables on a page?

It’s true: driver table blocks on pages cover most of what models can do. However, models currently support two key features that driver table blocks do not:

  1. Grouping drivers for better organization.
  2. Expanding drivers by dimensions

We know the line between models and pages can feel blurry. We’re actively working toward merging them into a single, more unified concept in the near future.

Creating a model

Start by clicking the + button next to a section or page in the sidebar. The new model will appear nested under that section or page.

Select Model as the type and give it a clear name, along with an icon or emoji for easy identification.

Adding & removing drivers

Adding, removing, and deleting drivers in a model works exactly the same way as in a driver table block on a page. Learn more in this guide.

Additional customizations

Just like in driver table blocks on a page, models allow you to: