A registry platform for authorities managing vessel ownership records. Powers Småbåtsregistret.
Designed to be understood at a glance.
Modern software should be easy to understand visually. Large interface previews allow visitors to immediately grasp how the product works.
Use this section to show real workflows, dashboards, or important screens. Screenshots are often the most convincing part of a product page.
Core functions, presented as an internet service: clear, composable, and easy to understand.
Structured records with identifiers, specs, documents, and history.
Transfers and updates that preserve chain-of-ownership over time.
Queues for review, clarification, approval, and rejection.
Public or restricted lookup patterns depending on policy.
Fast search, bulk actions, and controlled corrections.
Exports for oversight, compliance, and policy analysis.
Drop in screenshots later—this layout is designed to feel like a real web app.
Registry operations as repeatable flows. Short steps, clear outcomes.
Design principles that matter in public registries.
Validation and history-first design to keep records correct and traceable.
Roles, permissions, and decision attribution for accountability.
Backups, monitoring, and disciplined change management.
Short answers, no walls of text.
Småbåtsregistret is one implementation. Boat Registry is the reusable engine behind it.
Yes. Deployments typically configure fields, workflows, permissions, language, and policy rules.
Yes. Visibility rules are configurable so different roles see different data.
We integrate via APIs. Common integrations include identity/SSO, payments, messaging, and data exchange.
The best product pages rely heavily on visuals. Large interface previews and diagrams reduce the amount of text required while helping visitors understand how the system works.
This space is intentionally large and airy to give screenshots room to breathe.