# What a module costs to run

What's included, what's metered, and where a workspace sees its usage by module.

Good news first: most of what your module borrows from the platform costs nothing extra. A few services are **metered**, meaning the workspace pays for how much it uses. Knowing which is which helps you build a module that's kind to its users' bills, and lets you answer "what will this cost us?" with a straight face.

## Included

Part of every workspace, at no extra charge for your module to use:

| Included | |
|---|---|
| Your module's own tables and data | Users, roles and permissions |
| Module settings | Locations |
| Services between modules, and events | Schedules and triggers |
| Notifications | Email, through the workspace's own mailbox |
| Public pages and signing links | Charts and 3D on your screens |
| Python packages | Calls to outside hosts (the outside service may bill the workspace itself) |

All of a workspace's modules run together in one module home, sized by the workspace's **package**. A heavy module uses some of that room. When the workspace runs near its limits, its Workspace Admins get a notice.

## Metered

| Metered | What's counted | Good habits |
|---|---|---|
| **Storage** | Files and photos kept, beyond what the package includes | Make thumbnails; don't keep copies you don't need |
| **Database size** | The workspace's data, beyond what the package includes | Don't log every click |
| **AI** | Words the AI reads and writes, by model, on AI keys Data Visions provides | Pick the smallest model that does the job; reuse instructions |
| **Compute jobs** | How long each job runs, by CPU or GPU type | Size outputs sensibly; cancel jobs nobody needs |
| **Maps** | Map loads and address lookups, per 1,000 | Save the map position on the record instead of looking the address up again |

**AI on the workspace's own key** isn't billed by Data Visions at all: the AI provider bills the key's owner, and the usage still shows so the workspace can see it. On keys Data Visions provides, AI comes out of the workspace's **AI credits**.

**Maps are off until approved.** When your module declares that it uses maps, the Workspace Admin sees the service, its price and your reason when installing, and approves or declines it under **System settings › Billing › Service requests**.

**Bridge use and portal accounts** are on the platform's list of services that may be metered later. They aren't lines on the bill today, but build as if they were: no busy loops.

> **Modules your workspace built itself** carry no module charge. A Marketplace module may have a monthly price of its own, shown as its own line on the bill.

## Usage by module

A Workspace Admin can see where things go:

1. **System settings › Billing › Monthly bill**: the month so far, each part of the bill, and how each line is worked out.
2. **System settings › Billing › AI usage**: cost **By module**, **By user** and by model, with the calls and the text read and written behind each figure.
3. **System settings › Usage and adoption**: **Module adoption**, with active users, screen views, requests and AI sessions per module, and modules nobody uses.
4. **System settings › Marketplace › My modules**: how much each installed module was used in the last 30 days.

For AI to land under your module's name, run it through your module's agent or the platform's AI helpers. They log every call for you.

## Ask the Module Builder

> *"Before publishing, review my module for anything metered: storage, AI calls, maps and compute. Tell me where it could cost the workspace more than it needs to."*

```json
// For developers: module.json — declare paid services with a plain reason
"platform_services": [
  {"code": "MAPS", "why": "The job screen shows each site on a map", "optional": true}
]
```

## Good to know

- **Only Workspace Admins** see Billing and Usage and adoption.
- **Usage takes a little while to count.** Billing has **Refresh** for the latest.
- **Say it in your description.** If your module stores lots of video or leans on AI, say so, so nobody is surprised.
- **Mark a paid service optional** when your module still works without it, and say how in the reason. A Workspace Admin who declines maps still gets a working module.


Source: https://datavisions.ai/docs/creators/platform-services/what-a-module-costs-to-run
