UrbaHiveUrbaHive
    Launch App

    Everything you need to map your IT landscape together

    UrbaHive brings together in one platform what you need to map an IT landscape: a repository of applications, flows and servers, diagrams generated from that repository, business process mapping, a capability coverage matrix, impact analysis, ArchiMate import/export and a connector for AI agents. Built for SME and mid-market IT teams, without the heaviness of enterprise architecture suites.

    Application mapping: inventory, flows and servers

    One repository instead of scattered spreadsheets

    UrbaHive describes your IT landscape as a structured repository: programs, applications, flows, servers, infrastructures and people. Each application record holds its vendor, technical stack, hosting server, responsible person and technical architecture document. Status follows a typology your organisation defines itself, and custom fields cover what the standard model leaves out.

    • Application record: program, status, vendor, technical stack, internal or external service, server, architecture document and its version, responsible person and contacts
    • Flows between applications: source, target, type, frequency, one-way or bidirectional
    • Servers and infrastructures, with their location
    • Custom fields: 7 field types on 7 object types, included in search

    Diagrams generated from the repository

    Two views built from your data, not drawn by hand

    You do not draw the diagrams: UrbaHive generates them from the repository. The application-flow diagram groups applications by program and draws the flows declared between them; the infrastructure diagram shows servers and the applications they host. To correct a diagram, you correct the record behind it: there is nothing to redraw.

    • Application-flow diagram, grouped by program
    • Infrastructure diagram: servers and hosted applications
    • PNG or PDF export of the flow diagram, PDF export of the infrastructure diagram
    • The layout you arrange is saved locally in your browser

    Business process mapping, linked to your IT

    Describe who does what, and with which applications

    The catalogue organises your processes on two levels, by domain, with an owner, a linked business capability, a monthly volume and a status (draft, validated, deprecated). The editor describes each step: manual, semi-automated or automated execution, average duration, waiting time, RACI actors and the applications used. It is not a BPMN 2.0 modeller: its purpose is to link the business to IT and show where to act, not to reproduce the full notation.

    • Four step types (activity, decision, event, sub-process) and up to 3 labelled branches per decision
    • Flow view and swimlane view (one lane per role), PDF export of the process map
    • Optimisation score from 0 to 100 per process, automatable hours per month and top 10 automation opportunities
    • Risk signals: no owner, not reviewed for 12 months, knowledge held by a single person

    Business capabilities and impact analysis

    What each application covers, what each change touches

    Business capabilities form a hierarchy, each with its criticality and owner. The coverage matrix crosses capabilities with applications: it flags capabilities that no application covers and those covered by more than four. Impact analysis starts from an application, server, infrastructure, process, capability, program or person and shows its direct dependencies, upstream and downstream.

    • Capabilities × applications matrix, with a criticality on each link
    • Flags uncovered capabilities and redundancies (more than 4 applications)
    • Direct dependencies, one level deep, upstream and downstream
    • Objects shown on five layers: technical, application, functional, business, people

    ArchiMate and JSON import and export

    An exchange format, not an ArchiMate modeller

    UrbaHive imports and exports two formats: its own JSON and the ArchiMate Open Exchange Format (XML). A model built in Archi, or in any tool that exports that format, can therefore be imported, and your repository can go back to those tools. UrbaHive is not an ArchiMate modeller: it has no notation editor and does not handle the Strategy, Motivation and Implementation layers.

    • Before import, each item is marked as created, updated or ignored
    • ArchiMate export: applications, programs, vendors, roles, servers and infrastructures, architecture documents, flows
    • Three generated views in the exported ArchiMate file
    • UrbaHive JSON format, for both import and export

    AI connector (MCP server)

    Your AI assistant reads and updates the repository

    UrbaHive exposes an MCP server: an AI agent can query the repository and, if you allow it, add to it — applications, flows, servers, capabilities, processes and their steps, people. It works with Claude Desktop, claude.ai, Claude Code, Cursor, Windsurf, Codex and Devin. It is the only programmatic access to the repository.

    • 70 tools: 31 read, 39 write, no delete tool
    • Personal access token scoped to a single organisation; read by default, write optional
    • Limit of 60 requests per minute per token
    • Every call is written to the audit log

    Collaboration, audit log and EU hosting

    A shared workspace, clear roles, a record of every change

    Each organisation is a shared workspace: you invite colleagues by e-mail and give them one of four roles, which applies to the whole organisation. A colleague's change appears when the page is reloaded. The application is hosted on Vercel and Supabase, in European Union regions, where customer data is stored. NIS2 (art. 21) and DORA presuppose that you know your assets, their dependencies and who is responsible for them: the repository, the impact analysis and the audit log provide that inventory and traceability. UrbaHive has no dedicated compliance feature.

    • Four roles per organisation: Owner, Editor, Member, Viewer; a user can belong to several organisations
    • Audit log: creations, modifications and deletions with before/after values, viewable with filters in the app (not exportable)
    • Data encrypted in transit (TLS) and at rest
    • Encrypted backups, kept 30 days, restore tested monthly

    Ready to map your IT landscape?

    No credit card. Free plan available immediately.

    Start for freeSee pricing