An asset is one thing you manage — an application, a team, a data store, a business capability. Every asset belongs to an asset type, and the type decides what fields it has and what it can be related to.
A new workspace starts with a ready-made catalogue grouped three ways — business, applications and data, technology and operations — and you choose which of it to catalogue. The templates are a starting point, not a fixed schema: add a type later, or create your own when nothing offered fits.
Fields are typed. A choice field becomes a facet you can filter by and sorts in its own order — a risk rating sorts Extreme, High, Medium, Low — and any field you add appears in the grid, the detail panel, filters and exports.
The inventory is flexible underneath and opinionated on top: asset types, fields and relations are yours to define, and the AI proposes them from your own data.
Drop a CSV or Excel workbook — several sheets are fine — or paste tabular text straight out of a spreadsheet. Whatever lands is read against your workspace's profile, the industry and scale you set when you created it.
No template to fill in first and no column-mapping screen. The AI proposes the asset types, fields, relations and the assets themselves.
Start with whatever you have. The map that comes out of it is what drives the data to improve.
When the proposal is ready, What will be created summarises it: a count per asset type, each expandable to every name Aplas intends to create; a plain-language statement of how the assets will be linked; and the assumptions the draft used, each labelled with where it came from.
Confirm it and the assets are created. Change an assumption and re-draft. Nothing reaches the inventory until you say so.
Once the data is in: sortable columns, typed filters, a facet rail, bulk edits, and a column picker that knows every field of the type. A saved set of filters and columns is itself a view, and any table exports to Excel exactly as shown.
Workspaces organize the estate — a production inventory and a staging copy, or one per division — and a recent-changes feed names who changed what and when.
Relations are typed, and any asset type can relate to any other: an application is owned by a team, realizes a capability, runs on a technology, consumes an API. Each relationship type carries a name for either direction and a colour of its own.
A connection can also be an asset in its own right — an integration, a feed, a sync job — with fields, an owner and a lifecycle, connecting one or more sources to one or more targets. Relations are what a map draws as roads and regions, and what a graph lays out.
Table
The whole catalogue as a sortable, filterable table — every asset type in one place.
Search
Free-text search across every asset, with facets for type, owner and location.
Five published views of one inventory, open to exploreVisit the showcase