Studio
The visual modelling environment. Design an ontology or a property graph schema, import one you already have, and generate the mappings from it.
Free trial
Fourteen days of the platform, in your own account
The trial is the real thing rather than a sandbox: Studio, the Transformers and a Writer, deployed where your data already is. There is nothing to download and no account to create, because it runs in your infrastructure rather than ours. It starts with a conversation, and most people get more out of it if that conversation is a demo first.
Get in touch
Tell us where it needs to run
Which cloud, and roughly what you want to load. That is enough for us to send the right guide and to have something useful to say when we reply. If you would rather see it before you deploy it, say so here and we will set up a demo instead.
- You are sent the next-steps guide straight away
- A person replies to help with the deployment
- Fourteen days from the day it is running, not from today
- length
- 14 days
- runs in
- your AWS, GCP or own hardware
- includes
- Studio, Transformers, a Writer
- rather see it first
- book a demo
- questions
- explore@graph.build
trial enquiry
name, work email, target cloud
This is a message to us, not a login. There is nothing to log into: the platform runs in your account. You get the guide immediately and a person shortly after.
What you get
All three component types, not a viewer
A trial that can only model is a trial that cannot answer the question people actually have, which is whether the graph ends up in their database.
Transformers
Point them at your own sources. SQL, Kafka, JSON, CSV, XML, spreadsheets and REST all have a Transformer, and they apply the mapping the model produced.
output RDF or CSV
A Writer
Loads the result into your graph database over SPARQL, Cypher or Gremlin. This is the step that turns a trial from an evaluation into something you can show people.
targets your database
Help getting it running
Someone from the team walks the deployment with you and stays reachable for the fortnight. The point of a trial is a real result, and a fortnight spent on a Helm chart is not one.
support for the full 14 days
Should I do this or book a demo?
A demo, almost always, and then this. Forty-five minutes on your own domain with nothing to install will tell you more than the first three days of a trial, because it answers whether the platform fits your problem before you spend a fortnight finding out. Come to the trial knowing what you want to build and the fourteen days are worth having.
Do I get a login immediately?
No, and that is deliberate rather than a queue. The platform runs inside your own account, so there is nothing for us to log you into. Sending this form gets you the next-steps guide, and we get in touch to help stand it up in your environment.
Where does it run, and what does it need?
On AWS, on Google Cloud, or on your own hardware. The components are containers, so the requirement is somewhere to run containers and network access to whichever sources and graph database you want to use. The architecture page has the detail.
Does my data leave our infrastructure?
No. That is the main reason the trial is deployed rather than hosted. Sources are read inside your account, transformed inside your account, and written to a database inside your account.
What happens at the end of the fourteen days?
Nothing automatic and nothing deleted from your side. Whatever you modelled is a set of standard files, OWL and RML, which are yours either way. If you want longer because a source took a while to get access to, ask.
Can we extend it, or run a second one later?
Yes to both, and neither is unusual. Getting access to a source inside a large organisation routinely takes longer than the trial does, and a fortnight that was mostly spent waiting for a database credential is not a fortnight anyone learned from. Ask.