Skip to content
Prolincur Technologies

AI agents that understand maps, models and drawings

We build AI that works with spatial and engineering data, not just text: assistants that query GIS data with real tools, knowledge graphs that give agents connected context, and recognition of drawings and scans.

Why the data does not work together

01

Agents cannot read spatial data

Language models do not understand coordinates, geometry or layers, so answers about places are guesses.

02

Too much context, not the right context

An agent searching a whole enterprise graph gets lost. It needs the slice relevant to the place and decision at hand.

03

Drawings locked in images

Floor plans and engineering drawings exist only as scans, photos or PDFs that software cannot use.

04

Unlabeled 3D data

Reconstructed meshes and point clouds are one surface, with no idea which part is which object.

Software we build for this

Delivered as a module inside your product or alongside your enterprise stack, on open standards and without lock-in.

Delivered

Spatial AI assistant

An MCP server and conversational interface over your GIS data and analytics, built into your product.

Delivered

Knowledge graphs for twins and agents

Ontology and data in a graph database, with reasoning to infer links between assets and places.

Delivered

ML segmentation of scans and meshes

Semantic segmentation and classification of reconstructed 3D data.

Fixed-price accelerator

Drawing to CAD

Scans and images of engineering drawings converted into SVG and DXF vectors with VectraXD.

In development

Floor plan and drawing recognition

Images of floor plans and engineering drawings turned into structured data: rooms, walls, symbols and text. Part of VectraXD.

Open standards, no lock-in

  • MCP
  • FastMCP
  • PostGIS
  • AWS Neptune
  • RealEstateCore
  • Ontologies
  • Open3D
  • Python
  • VectraXD
  • 3D Tiles
  • IFC
  • glTF
  • GeoJSON
  • OGC services
  • Self-hosted or on-prem

Prolincur is a member of NVIDIA Inception and Microsoft for Startups Founders Hub.

From first call to long-term support

  1. 01

    Discovery call

    30 minutes with an engineer, under NDA if you need one.

  2. 02

    Technical discovery

    1 to 3 weeks: requirements workshop, code and data review, and a proof of concept for the risky parts.

  3. 03

    Proposal

    Phased plan, team, estimate and engagement model.

  4. 04

    Delivery

    Two to three week iterations, with a demo every sprint.

Common questions

Which AI models do you work with?

We build around the model your team prefers and expose your data through MCP, so the assistant uses real tools instead of guessing.

Is our data sent to a public AI service?

Only if you choose that. We can deploy inside your cloud or on-prem, with the model and data under your control.

Is floor plan recognition available now?

It is in development as part of VectraXD. Drawing vectorization to SVG and DXF is available today.

Need this in your product?

Tell us what you are building. You will talk to a software engineer from the first call.