Modelling in Studio
Building classes, properties and relationships on the canvas, and what the same model looks like as RDF and as a property graph without being drawn twice.
Book a demo
Bring a domain and we will model it in front of you
Not a slide deck with a recorded product tour in the middle. Forty-five minutes in the real thing, on something you actually care about, with whatever you have already got.
Request a session
Tell us what you would want to see
One line about the domain is enough. It lets us set up something relevant beforehand rather than starting from an empty canvas while you watch.
- 45 minutes, your data, no installation
- You keep whatever we model
- No obligation to buy anything
- format
- video call, screen shared
- who joins
- an engineer, not a rep
- bring
- a schema, an OWL file, or a photo of a whiteboard
demo request
name, work email, what you are modelling
Used to arrange the session and to follow up once. Not a drip campaign.
The session
An overview, then straight to the part you care about
The first ten minutes are the same for everyone. The rest is shaped by what you said in the form.
Mapping a real source
Pointing a Transformer at a database, an API or a file you brought, and mapping it to the model without writing an ingest application.
minutes 10 to 15
Writing to a database
The run, the counts, and the same output written to whichever graph database you are considering. This is usually where the vendor independence stops being a claim.
minutes 5 to 10
Whatever you asked about
Provenance, change data capture, the MCP server, deployment inside your own account, or how any of it survives a model change. Your questions, not our agenda.
minutes the rest
Do I need to prepare anything?
No. A sentence about the domain in the form is enough. If you do want to bring something, a database schema, an existing OWL or RDFS file, a sample CSV or a photograph of a whiteboard all work, and any of them make the session more useful than a generic dataset would.
Do you need access to our data?
No. Nothing is installed and nothing is connected. If you want to see your own source mapped we can do that on a sample you are comfortable sharing, but most sessions run on something we set up from your description.
Who should come?
Whoever will have to live with the model. That is usually a data architect and someone who knows the domain, and the second one matters more than people expect. Bring an engineer too if deployment is the question you are really asking.
What happens afterwards?
You get whatever was modelled during the session, as a file. We follow up once. If the answer is that this is not for you, that is a fine outcome and we would rather reach it in forty-five minutes than in three months.