--- title: Graph Build Studio - No-Code Graph Database Building description: The Graph.Build Studio enables non-developers to work on graph database creation, including knowledge graphs, in a way that fits with set team standards. --- [Skip to content](https://graph.build/graph-build-studio#main) [![graph.build](https://graph.build/hubfs/raw_assets/public/graphbuild-theme/images/logo-secondary-reverse.svg)](https://graph.build/) Menu - Platform - AI context [Context for AI](https://graph.build/ai-context) [Semantic layer](https://graph.build/semantic-layer) [GraphRAG](https://graph.build/graphrag) [MCP & agent access](https://graph.build/mcp) [Ontologies explained](https://graph.build/resources/ontology) - Resources [Blog](https://graph.build/blog) [Graph fundamentals](https://graph.build/resources) [Documentation](https://graph.build/documentation) - Company [About us](https://graph.build/about) [Consulting](https://graph.build/consulting-services) [Contact](https://graph.build/contact) [Book a demo](https://graph.build/enquire/book-a-demo) Model [Studio](https://graph.build/graph-build-studio) [Visual graph modelling](https://graph.build/graph-modelling-tool) [Ontologies & vocabularies](https://graph.build/platform-architecture#ontology) Transform [Transformers](https://graph.build/graph-build-transformers) [Knowledge graph ETL](https://graph.build/knowledge-graph-etl) [Change data capture](https://graph.build/graph-build-transformers#cdc) Write [Writers](https://graph.build/graph-build-writer) [Database compatibility](https://graph.build/graph-databases) [Deployment](https://graph.build/platform-architecture#deployment) You are here [The graph engineering lifecycle](https://graph.build/knowledge-graph-building) Design, configure, engineer, iterate and automate graph model production: the whole lifecycle, without writing bespoke ingest code for each project. Model [Studio](https://graph.build/graph-build-studio) [Visual graph modelling](https://graph.build/graph-modelling-tool) [Ontologies & vocabularies](https://graph.build/platform-architecture#ontology) Transform [Transformers](https://graph.build/graph-build-transformers) [Knowledge graph ETL](https://graph.build/knowledge-graph-etl) [Change data capture](https://graph.build/graph-build-transformers#cdc) Write [Writers](https://graph.build/graph-build-writer) [Database compatibility](https://graph.build/graph-databases) [Deployment](https://graph.build/platform-architecture#deployment) AI context [Context for AI](https://graph.build/ai-context) [Semantic layer](https://graph.build/semantic-layer) [GraphRAG](https://graph.build/graphrag) [MCP & agent access](https://graph.build/mcp) [Ontologies explained](https://graph.build/resources/ontology) Resources [Blog](https://graph.build/blog) [Graph fundamentals](https://graph.build/resources) [Documentation](https://graph.build/documentation) Company [About us](https://graph.build/about) [Consulting](https://graph.build/consulting-services) [Contact](https://graph.build/contact) [Book a demo](https://graph.build/enquire/book-a-demo) Platform / Studio # Where the model gets made Studio is the no-code interface at the centre of the platform, and because the Transformers and Writers are wired into it, it is closer to an IDE for graph production than a modelling tool. Model, mappings, test runs and generated queries are all in one place, on your real data. graph.build supply-chain.etl Semi Structured Model Designer Generate Model Input sample.json Supplier LegalName DunsNumber Part Description LeadTimeDays --- IRI Config http://graph.build/ontology/ supply-chain.ontology · v14 1 hasPart hasLegalName hasDescription hasLeadTime {DunsNumber} {Supplier} {PartNumber} {Part} {LegalName} {Description} {LeadTimeDays} 2 3 supply-chain.etl · mapped from sample.json Output Model Test Model Results rdf:type gbo:Supplier hasLegalName Northgate Ltd hasDuns 213847561 hasLeadTime 14 (integer) 8 triples · subject, predicate, object download as n-quads 4 8 triples generated · 0 unmapped 2026-08-13 11:19 1 The source, parsed. sample.json is read into its fields. Drag one onto the canvas and the mapping exists. There is no ingest code to write for it. 2 Identity, not a row number. The line above the class name is the field the IRI is built from, so the same supplier resolves to the same node across every source that mentions it. 3 The predicate is the edge. Relationships are named on the connector rather than beside it, because the name is the relationship. That is what ends up in the triple. 4 Test before you write. Run the model against the sample and read the triples it produces, before anything is written to a database. Visual modelling ## One model, both formalisms, generated Semantic and property graph models are built in the same editor, from the same source data. When the design is done you press Generate, and Studio produces the shape the target expects: an ontology in OWL and RDFS on the semantic path, node and edge definitions on the property graph path. Both are standard, both are readable, and both are yours. RDF · ontology Property graph · schema same source model · supply-chain.model v14 Class hierarchy gbo:Supplier owl:Class gbo:hasLegalName xsd:string gbo:hasDuns xsd:string gbo:hasRiskTier xsd:string gbo:Part owl:Class gbo:hasSku xsd:string gbo:hasLeadTime xsd:integer gbo:Site owl:Class gbo:hasCountry xsd:string gbo:hasPart owl:ObjectProperty gbo:madeAt owl:ObjectProperty Generated ontology owl · turtle @prefix owl: . @prefix rdfs: . @prefix xsd: . @prefix gbo: . ### Classes ### gbo:Supplier a owl:Class . gbo:Part a owl:Class . gbo:Site a owl:Class . ### Object properties ### gbo:hasPart a owl:ObjectProperty ; rdfs:domain gbo:Supplier ; rdfs:range gbo:Part . gbo:madeAt a owl:ObjectProperty ; rdfs:domain gbo:Part ; rdfs:range gbo:Site . ### Datatype properties ### gbo:hasLeadTime a owl:DatatypeProperty ; rdfs:domain gbo:Part ; rdfs:range xsd:integer . Labels & properties :Supplier node label legalName string dunsNumber string riskTier string :Part node label sku string leadTimeDays integer :Site node label country string HAS\_PART relationship MADE\_AT relationship Generated schema node & edge headers # node files, one per label supplier.csv :ID,legalName,dunsNumber,riskTier,:LABEL part.csv :ID,sku,leadTimeDays:int,:LABEL site.csv :ID,country,:LABEL # edge files, one per relationship type supplier\_part.csv :START\_ID,:END\_ID,:TYPE part\_site.csv :START\_ID,:END\_ID,:TYPE # property types are declared in the header # :int :float :boolean :date # no rows here on purpose, this is the shape # the data arrives when a Transformer runs mapping ### Source fields become meaning Drag a column onto an attribute and the mapping exists. Where the source needs work first, over a hundred built-in functions handle the reshaping, including parsing, lookups, concatenation, date and unit normalisation, and you can register your own for the cases that are only yours. Every mapping is a file that lives with the model and versions with it. The consequence: a published ontology can inform the mapping or restrict it, so a mapping that does not conform is caught while somebody is making it. Records that fail during a run go to a dead letter queue, which is a list you can work through and reprocess rather than a number that went down. studio · entity · Supplier · v14 gbo:Supplier/213847561 hasLegalName Northgate Ltd gbo:Supplier/213847561 rdf:type gbo:Supplier gbo:Supplier/213847561 hasPart gbo:Part/HX-8841 gbo:Part/HX-8841 hasLeadTime 14 (integer) n-triples 8 emitted, validated against supply-chain.ontology all passed unmapped: 0 · quarantined rows keep their reason Ontology governance ## One definition of Customer, and a record of every change to it Governance here is not a permission matrix. It is the ontology and its history. You agree what a Supplier is, generate it, publish it, and every model built afterwards is either informed by that definition or restricted to it, so the second team to arrive cannot quietly invent a second Supplier. version control ### Every change is a commit Studio is backed by git. Saving a model writes a revision, and the history pane lists them with who made the change and what the model looked like at that point. Commit a named checkpoint yourself when a version is worth marking, restore an earlier revision when a direction turns out to be wrong, or make a copy from one and explore without touching what everyone else is using. Roles stay deliberately simple, an admin manages the instance and its users and everyone else builds, because what protects the model is the history rather than the seat. The consequence: “who changed the definition of Customer, and when” is a question with an answer, and going back to the version before they changed it is a click rather than a restore from backup. PersonCardOntology · history select a revision to view 14/08 10:15 admin · manual commit 8 nodes · 6 edges 14/08 09:52 admin · saved 8 nodes · 5 edges 13/08 12:19 admin · saved 7 nodes · 6 edges 13/08 10:04 admin · restored 11/08 7 nodes · 6 edges 11/08 15:38 admin · manual commit 7 nodes · 6 edges Collaboration ## One person edits. Everyone else has it open. Studio is multi-user without being simultaneously multi-writer, which for a governed model is the right way round. One person holds edit control while the rest have the model open read-only, and control is handed over deliberately rather than raced for. Because the model is visual, the subject-matter experts who know what a Supplier actually is can follow it, and take the pen, without learning a query language. ontology model designer · edit control 1 editing · 3 read-only Input Class Literal hasPart madeAt coveredBy Supplier d.mercer · has control Part Site Contract activity 09:41 d.mercer added hasRiskTier 09:36 control handed to d.mercer 09:20 a.okafor released control 08:58 supply-chain.model published v14 one writer at a time · handover is explicit · every publish carries a version Where it sits ## Studio authors it. Transformers run it. Writers land it. Three component types, two hand-offs, and both hand-offs are files you can read. Every one of them is a Docker container, deployed on-premise or in your own cloud. ### Studio Authors the model and the mapping files, validates them, publishes a version. outputs · model + .map publishes v14 ### Transformers Execute the mappings against SQL, APIs, Kafka and files. Resolve identity, quarantine what does not fit. outputs · resolved records hands off batches + cdc ### Writers Emit your database's native load in insert or update mode, and keep it current through CDC. outputs · your graph database ## See Studio on your own model Bring a source system and the thing you have been trying to model. A working session gets further than a demo. [Book a demo](https://graph.build/enquire/book-a-demo) - 45 minutes, your data, no installation - You keep whatever we model - No obligation to buy anything Platform [Studio](https://graph.build/graph-build-studio) [Transformers](https://graph.build/graph-build-transformers) [Writers](https://graph.build/graph-build-writer) [Database compatibility](https://graph.build/graph-databases) [Platform architecture](https://graph.build/platform-architecture) AI context [Context for AI](https://graph.build/ai-context) [Semantic layer](https://graph.build/semantic-layer) [GraphRAG](https://graph.build/graphrag) [MCP & agent access](https://graph.build/mcp) [Ontologies explained](https://graph.build/resources/ontology) Resources [Blog](https://graph.build/blog) [Graph fundamentals](https://graph.build/resources) [Choosing a graph database](https://graph.build/graph-databases) [How to build a knowledge graph](https://graph.build/knowledge-graph-building) [Documentation](https://graph.build/documentation) Company [About us](https://graph.build/about) [Consulting](https://graph.build/consulting-services) [Contact](https://graph.build/contact) Legal [Privacy policy](https://graph.build/privacy-policy) Get in touch No newsletter. If you want to talk about a model, or want to be kept posted, the contact form is the way in. [Contact us](https://graph.build/contact) - © 2026 Graph.Build · A trading name of Data Lens Labs Ltd, registered in England & Wales, company number 12483318 [![graph.build](https://graph.build/hubfs/raw_assets/public/graphbuild-theme/images/logo-secondary-reverse.svg)](https://graph.build/) ```json { "@context" : "http://schema.org", "@type" : "WebPage", "about" : [ { "@type" : "Action", "name" : "Graph Modelling" }, { "@type" : "Action", "name" : "Building a Knowledge Graph" } ], "description" : "The Graph.Build Studio enables non-developers to work on graph database creation, including knowledge graphs, in a way that fits with set team standards.", "name" : "Graph Build Studio Graph Modelling Tool", "url" : "https://graph.build/graph-build-studio" } ```