Inventory / WMS
Built for stock movement, not files, licences, spaces, or people.
Every company has things that need to be tracked, assets, licences, people, spaces, vehicles, consumables, and files. Most track them in spreadsheets that no one trusts. Stocky Space is an operational registry that replaces the chaos with lifecycle rules, entity relationships, quantities, custom fields, and full audit history. If it matters to your operations, Space can track it.

The gap
Most systems handle one slice of operational reality well. Space is built for teams that need one entity model across many categories, processes, and measurements.
Each tool stops at its own boundary, so teams still stitch categories together because every system understands only its own slice of the entity.
Inventory / WMS
Built for stock movement, not files, licences, spaces, or people.
EAM
Strong for maintainable assets, weak when the operation depends on many entity types.
CMDB
Good at relationship mapping, not at operational lifecycle control and quantity events.
Spreadsheets
Flexible until enforcement, history, and accountability start to matter.
One operating model across the whole entity. Space keeps identity, state, quantity, relationships, and capture rules on one connected record.
Configurable registry
One entity model with 11 archetypes out of the box, plus custom types when needed.
Lifecycle graph
Directed stages with role checks, required forms, SLAs, and execution control.
Measurement layer
UOM-aware quantities with split, merge, consume, and adjust operations.
Connected context
Relationships, assignment, dynamic attributes, and audit history on the same record.
Three pillars
Space is built as a strict stack: core handles measurement, registry defines the entity, and lifecycle controls movement. Each layer adds capability without collapsing into one giant record model.
Space gives every entity a consistent home while still adapting labels, fields, permissions, and validation to the type being tracked.
That is what lets operations teams stop buying separate tools for every trackable thing while still keeping the model specific enough to be useful.
Lifecycle orchestration
Lifecycle in Space is a directed state graph with rule enforcement, required capture, SLA control, and accountable execution.
The path is explicit, so the operation stays explainable.
Whether you are moving devices through inspection, files through review, or spaces through readiness states, the same lifecycle engine governs how records can progress.
What the engine enforces
Clusters and stages describe the real path an entity can take, not just its current label.
Transition rules stop invalid moves before state, quantity, or compliance data goes wrong.
SLA thresholds and execution leases keep ownership explicit while work is in motion.
Control surface
Permitted transitions
Only valid next stages are offered for the current state.
Required capture
Mandatory forms and validation block movement until the record is complete.
SLA + leases
Timers, escalation, and execution control help enforce operational discipline.
Space can model receiving to deployment, intake to approval, incident to closure, or any other directed path that needs policy and history.
Measurement + UOM
Measurement in Space is not a side field. It is a first-class layer for quantity-aware operations, unit conversion, and lineage preservation.
Track measurable entities in the unit teams actually use while preserving a canonical quantity underneath.
Break a lot, batch, or quantity into child records without losing where each child came from.
Combine quantities, record consumption, and keep the event trail explainable after the fact.
Correct shrinkage, wastage, repacking, or count fixes without overwriting what happened before.
This is what lets Space handle consumables, components, and mixed-unit workflows that break simpler inventory-style trackers.
Example quantity flow
Step 1
Receive 200 kg into the source record.
Step 2
Split it into smaller lots or child entities for downstream work.
Step 3
Consume, merge, or adjust quantities as the process changes the item.
Step 4
Review the lineage tree when someone asks where the result came from.
Split, merge, consume, adjust
Operations
Kg, liters, pieces, packs, and more
Units
Relationships
Registry records are not isolated rows. Space supports multiple relationship mechanisms so the model matches the way entities actually connect in the business.
Relationship map
Campus -> Building -> Floor -> Room -> Rack -> Server
Laptop A -> replaces -> Laptop B
Starter Kit -> contains -> Laptop + Mouse + Bag
Resin Lot 42 -> split into -> Lot 42A + Lot 42B
Printer -> compatible with -> Cartridge XThis is how Space can model physical containment, replacement chains, grouped kits, compositions, and operational associations without forcing everything into one brittle relationship type.
Relationship explorer
Model containment, replacement chains, grouped kits, BOMs, and directional associations on the same registry record.
Typed links
Directional or bidirectional links such as replaces, depends on, or compatible with.
BOM / composition
Represent what something is made of, with quantities and units where needed.
Kits / bundles
Group multiple items for operational execution without losing the underlying records.
Variant groups
Keep peer variations connected when the same entity exists in multiple forms.
Containment
Model physical nesting like building to floor to room to rack to server.
11 archetypes
Every tenant gets eleven system types out of the box, and each one can adapt labels, visibility, and validation without breaking the shared model.
Track maintainable physical or digital assets, with serial relabeled to Asset ID when needed.
Model entitlements with issuer, licence key, lifecycle position, and linked ownership.
Use the same registry model for cases, records, claims, dossiers, and other reference-driven files.
Track employees, patients, students, or candidates as lifecycle-aware entities instead of side records.
Handle fleet records with make, model, year, VIN, and downstream lifecycle events.
Represent rooms, bays, parking spots, sites, or facilities with location code and containment structure.
Integration points
Space is not meant to live alone. It becomes the entity layer other StockyPro apps attach to when they need shared records, relationships, and history.
Transition logs, quantity logs, SLA escalation, and execution all attach back to the same registry entity.
Dynamic fields extend the entity without hardcoding every domain-specific attribute into the base model.
Registry items can attach to deals when revenue work needs the same entity context.
Items can stay linked to people, organizations, owners, and operational stakeholders.
Connected surface
Role
Space acts as the central entity layer
Result
Other apps attach to the same record instead of recreating it
Benefit
Less duplication, stronger history, cleaner cross-app context
Audit trail
Auditability is built into the operating model, so reviews do not depend on reconstructing history from separate systems.
Transitions and quantity operations are preserved as events instead of being flattened into the latest state.
Every significant move keeps the responsible user or team attached to the event.
Review sequences in order when you need to explain what happened and when it happened.
Form payloads, linked contacts, files, and related records stay attached to the event context.
Example event stream
AST-2407 moved Receiving -> Active
09:24
Inspection form captured and linked to the asset record.
CON-038 split into four child lots
11:10
Source quantity reduced and lineage tree updated automatically.
FIL-1021 advanced Review -> Approved
16:45
Reviewer, timestamp, and submission payload preserved in the audit log.
Each event can include
Market positioning
Space sits between categories: broader than EAM or CMDB, stricter than spreadsheets, and more operationally expressive than inventory-only tools.
EAM
Strong for maintenance-centric assets, weak when the domain extends beyond classic asset management.
Space: Space supports maintainable assets and also licences, files, people, spaces, vehicles, consumables, and custom entity types.
CMDB
Excellent for IT configuration relationships and impact mapping, but not built for operational lifecycle execution.
Space: Space adds directed lifecycle control, quantity-aware operations, and broader entity coverage beyond IT infrastructure.
Inventory / WMS
Good at stock counts, warehousing, BOMs, and pick-pack-ship workflows for goods.
Space: Space adds configurable archetypes, lifecycle graphs, SLA enforcement, and entities that are not just stock.
Spreadsheets
Flexible enough to start quickly, but enforcement, history, relationships, and lineage stay manual and fragile.
Space: Space keeps the flexibility of configuration while enforcing rules, preserving history, and linking business context to the record.
Simple pricing
Flat pricing for the full Space stack, from configurable registry through lifecycle and measurement.
See complete pricing and rollout details on the pricing page.
Visit pricing pageRs. 5,000/ month
Start with ProfessionalFor teams over 25 users, deeper integration needs, or more structured rollout support.
Research next
Keep the operations-system evaluation connected to comparisons, category-intent pages, and proof.
See where a universal entity registry differs from narrower asset administration tools.
OpenReview the workflow requirements for lifecycle control, auditability, and quantity-aware operations.
OpenRead how organizations use Space to manage lifecycle-heavy operational systems.
OpenWhat teams ask when evaluating Space as their entity registry.
Ready?
Replace disconnected trackers with one configurable registry, directed lifecycle control, quantity-aware operations, and auditable history.