Tosven is in pilot. Early access conversations are open for the first companies. Apply

Metadata engine

Define a record type once. Use it everywhere.

Builder turns one definition of fields, relations, lifecycle and permissions into a form, a list, an API, an agent tool and a Lens measure. It is configuration inside the product, so upgrades do not break it.

1
definition per record type
6
outputs: form, list, API, permissions, agent tool, measure
4
sensitivity classes that govern every field
100
custom fields per type, a limit set on purpose

Every company has records no vendor planned for

Read the documentation

A rental company tracks handovers. A maintenance company tracks site visits. A consultancy tracks permits. Standard software offers two answers: a spreadsheet beside the system, or a custom development project that has to be repaired at every upgrade. Builder is the third answer. You describe the record type once, in the product, and Tosven treats it like one of its own.

The definition holds the fields, the links to other records, the lifecycle and who may read or write what. From it Tosven derives validation, storage, lists with filters, permission checks, the audit trail and the tools an agent may use. Customers, the CRM module, runs on the same engine. Your own types therefore share its database, its permissions and its audit trail from the first record.

Builder

Record types, from draft to retired

Each type has a state of its own. Drafts can change freely. A published type keeps its field keys and field types for good. Built-in types are maintained by Tosven, and retired types stay readable.

Sample data · record types

What one definition gives you

01

Fields and relations

Text, number, money, date, select and link fields, plus child tables for lines. A link points to a real record, such as a customer or an order, never to a copied name.

02

Lifecycle

A type is either simple or documentary. Documentary records move from draft to submitted to cancelled, and a submitted record changes only in the fields you allow.

03

Permissions down to the field

Read, write, delete and approve are granted per type. Row filters and field redaction are applied inside the data layer, so lists, API responses and agent output all obey them.

04

Lists and filters

Every type gets a list with filtering, sorting and paging. One filter language serves lists, display conditions and access rules, and an unknown field is an error, never a silent gap.

05

Numbering series

Choose a unique id or a series such as SV-{YYYY}-{####}. The number is assigned in the same step that creates the record, from a counter per type and period.

06

Audit trail and events

Every change is written to one audit log with the changed fields, the actor and the definition version. Each change also emits an event that other modules can react to.

07

Agent tools

Described fields become search, read and propose tools for agents. An agent's proposal is a draft that a person submits. Tools for deleting or for changing permissions are never generated.

08

Indexes and uniqueness

Mark a field as indexed or unique and Tosven builds the index at publish time. Existing duplicates are reported before the rule applies, with the rows that cause them.

09

Versioned definitions

Definitions are published as versions. Adding a field takes effect at once. Tightening a rule first runs a scan of existing records and shows what would break.

In practice

Builder in three working examples

01

A new record type, published the same morning

Jonas Berg wants site visits recorded against customers and orders, not in a shared spreadsheet.

  1. 09:05Jonas BergCreates the type Site visit with twelve fields. Two of them link to the customer and the order.
  2. 09:20Jonas BergSets the lifecycle to documentary and the numbering series to SV-{YYYY}-{####}.
  3. 09:32Jonas BergGrants write to operations and read to sales. Marks the access code field as restricted.
  4. 09:40Jonas BergPublishes version 1. The form, the list and the permission checks exist from this moment.
  5. 10:15Laura VirtanenRecords SV-2026-0001 for Harju Tekniikka Oy, linked to ORD-2026-0193, and submits it.
02

A rule is tightened without breaking old records

After three months the team wants a mandatory meter reading on every site visit.

  1. 14:00Jonas BergMarks the field Meter reading as required and asks to publish version 4.
  2. 14:01Jonas BergReads the pre-flight scan: 37 submitted records have no meter reading. They are listed by id.
  3. 14:06Jonas BergChooses to enforce the rule for new writes only, from 01.11.2026.
  4. 14:07Jonas BergPublishes. Existing records keep their version, and the audit log records the change.
  5. Next dayLaura VirtanenTries to submit a visit without a reading. The form names the missing field and how to fix it.
03

An agent drafts, a person submits

Sanna Lind asks in the shared customer room for a follow-up visit at Nordlys AB.

  1. 11:02Sales agentSearches Site visit for Nordlys AB with the generated search tool and finds the last visit.
  2. 11:02Sales agentProposes a new visit as a draft. The customer is resolved by search, never by a guessed id.
  3. 11:20Antti KorhonenOpens the draft and moves the date to 21.10.2026.
  4. 11:21Sales agentIts own update meets a version conflict. It does not overwrite and reloads the current record.
  5. 11:25Antti KorhonenSubmits the visit. It appears as a record card in the Nordlys AB customer room.

Sample data

One definition

The definition is the single source, not one of several copies

In most systems a new record type means a table, a screen, an endpoint, a permission matrix and a report, written separately and kept in step by hand. In Builder all of them are compiled from the same definition and cached by its version number. When the definition changes, everything derived from it changes in the same step.

  • Validation, storage mapping and tool schemas compiled together
  • A version counter decides which compiled form is current
  • A reserved key prefix keeps your fields apart from built-in ones
  • Built-in types and your types are stored and secured the same way
Permissions

A field's sensitivity follows it everywhere

Each field carries one of four classes: public, internal, restricted or secret. That single flag decides who sees the value, whether it appears in default list columns, whether it may feed semantic search, and whether an agent tool may return it. Because redaction happens in the data layer, there is no screen, export or tool that forgets to apply it.

  • A closed set of verbs: read, write, delete, approve
  • Row filters per type, evaluated in the database
  • Secret values appear in the audit log only as a hash
  • Restricted fields need an explicit capability, also for totals
Agents and Lens

Agents and analytics read the same definition people do

A field with a description becomes part of a tool an agent can call: search, read, propose a new record, propose a change. Links are resolved by search, and a search returns at most fifty rows. Number and money fields are designed to become Lens measures with the same permissions and the same drill to the record. Measures for your own types are on the way.

  • No generated tool can delete permanently or change a definition
  • An agent proposal is a draft. Approval is a human submit
  • On a version conflict the agent never overwrites
  • Text fields can feed search, under the same live permissions
Upgrades

Configuration that survives every release

Custom code breaks because the vendor cannot see it. A Builder definition is data that Tosven reads on every release. A published field key and field type never change silently. Renaming or retyping is an explicit operation. Tosven never deletes a published field of a built-in type. It deprecates the field, reapplies your additions after an upgrade and flags anything left without a home.

  • Additive changes publish at once
  • Tightening changes are gated by a scan of existing records
  • Each record carries the definition version it was written under
  • Limits per type keep the model healthy: 100 fields, 15 indexed

In the field · Equipment rental company

Handovers, inspections and damage, in the same system as the invoice

An equipment rental company hires out lifts, compressors and site cabins. Its real process is not in any standard module: a unit is reserved, handed over with a checklist and photos, returned, inspected and sometimes charged for damage. In most companies that process lives in paper forms, a shared spreadsheet and the memory of the yard staff, while the invoice is written somewhere else by someone who was not there.

With Builder the company defines four record types: Equipment unit, Rental contract, Handover inspection and Damage report. Each links to the customer in Customers. The yard works from lists filtered by state. A damage report submitted at return carries the unit, the contract and the amount, so whoever prepares the invoice sees the inspection behind the charge. Nothing was programmed, and the next release leaves the types intact.

With separate tools

  • Handover checklists on paper, filed by date in the yard office
  • Unit availability kept in a spreadsheet one person maintains
  • Damage charges disputed because the evidence is somewhere else
  • A custom add-on quoted as a project, then frozen at upgrade time

In Tosven

  • Handover and return are records linked to unit and contract
  • Availability is a list of units filtered by lifecycle state
  • Damage report, inspection and contract reference each other
  • New fields are published by the operations lead, with a version

A working day

Sample data
  1. 07:00The yard opens the list of handovers due today: six units, each linked to its rental contract.
  2. 09:30A compressor goes out to Harju Tekniikka Oy. The handover inspection is submitted and locked.
  3. 12:10Jonas Berg adds the field Fuel level to Handover inspection and publishes version 3.
  4. 15:20A lift returns with a damaged guard rail. A damage report for 640,00 € is drafted and submitted.
  5. 16:45Sara Nyström prepares the invoice with the damage report and the inspection open beside it.

Status

Where it stands today

Live in pilot
  • Type definitions with published versions and retirement
  • Records with create, edit, submit and cancel, and conflict detection
  • Lists with one filter language and field redaction
  • Per-type permissions, audit log and change events
  • Numbering series, indexed and unique fields
  • Agent tools generated from described types. Customers runs on Builder
On the way
  • Type editor screen. In the pilot, types are published by the Tosven team
  • Generated form layouts for your own types
  • Custom fields and sections on built-in types
  • Declarative states and transitions beyond draft, submitted, cancelled
  • Lens measures and Channels record cards for your own types
  • Public REST API, webhooks and CSV or Excel import

Frequently asked

Questions and answers

hello@tosven.com

Is Builder a low-code platform?

No. Builder does not run scripts or custom code. It is a closed set of field kinds, lifecycle models, filters and permissions, the same set Tosven itself is built on. That limit is deliberate. Everything you configure can be validated, secured, audited and carried through an upgrade, which arbitrary code cannot promise.

What happens to our record types when Tosven is upgraded?

They stay as they are. A definition is data, not code, and a published field key and field type never change without an explicit operation. Tosven does not delete published fields of built-in types. It marks them deprecated, reapplies your additions after the upgrade and flags anything that no longer has a place.

Who can define a record type today?

In the pilot, record types are defined together with the Tosven team and published through the engine, because the editor screen is not released yet. The engine underneath is in use: the Customers module runs on it. The editor, generated form layouts and custom fields on built-in types are listed under what is on the way.

Are there limits?

Yes, and they are intentional. A type holds up to 100 custom fields, of which 15 can be indexed. Field keys and field types are fixed once published. These limits keep lists fast and stop a data model from decaying into hundreds of unused fields, a problem that is expensive to repair later.

Can agents work with our own record types?

Yes, within strict bounds. A described type gives agents tools to search, read and propose records. A proposal is a draft that a person submits. No generated tool deletes permanently, changes permissions or changes a definition, and an agent never has more access than its human manager. Ledger agent and Collections agent are the agents in production today.

Early access

Be among the first companies.

Tosven is in pilot. Tell us about your company and the tools you use today in a few sentences, and we will say plainly whether it is a fit.

sales@tosven.com · No card details and no commitment.