Dgraph, Welcome to Istari

Hello Dgraph community,

I wanted to take the opportunity to introduce myself - I’m Maggie Johnson-Pint, and I am the Vice President of Product and Engineering at Istari Digital - the new stewards of Dgraph. We are thrilled to welcome the Dgraph community to Istari!

You can read our official press release about this acquisition here - but as a long time open source maintainer and the new engineering owner of Dgraph, I wanted to connect with the community here directly, and try to address initial questions that might come up.

Who is Istari Digital, and why do you want an open source graph database?

Istari creates a platform for aerospace and mechanical engineers to convert vendor-locked engineering data into vendor-neutral formats, and leverage that data to create powerful workflows to validate designs of hardware. I often describe us as “GitHub for Planes”.

As AI technology has taken off, Istari has found a need to represent more complex data models and relationships inside distributed networks. Acquiring Dgraph enables us to accelerate delivery of new engineering data features to our customers, while ensuring performance, scalability, compliance with Department of Defense security policy, and our commitment to open data.

What happens next?

Our first priority at Istari, is to ensure that Dgraph is a well-maintained project for the community - something that only grows more important as we deepen our own usage. Raphael Derbier joins us from Hypermode, and will be the primary representative to the community going forward. We also have several members of the Dgraph engineering team joining us to ensure continuity.

We are only just beginning to develop an understanding of the exact roadmap for Dgraph, but we do know that we are excited to bring new data features that are impactful for our existing customers in the US Federal and Aerospace markets - many of whom are also Dgraph customers and users. With these customers as a focus, you can be assured we will be doubling down on performance, scalability, and security.

Looking forward to the journey ahead!

Maggie

5 Likes

Thank you for the update, great to hear that development continues on Dgraph!
Could you clarify the relationship with Hypermode? Will Hypermode still contribute to Dgraph? Also, will GitHub projects and the forum be migrated to an Istari namespace/domain? Looking forward to the next steps.

GitHub assets are migrated back to dgraph-io as we want Dgraph to stay an open-source project with its own place.
We are working at moving discuss and hosting the documentation. I let you know asap when doc and discuss have landed.

2 Likes

Interesting, hmm.

When the team has time @maggiepint Id be interested in your take on The Good, The Bad, The Ugly - State of Dgraph

1 Like

Which direction is Dgraph going in?

  • Double down on DQL (or other Graph languages)?
  • Fix the GraphQL problems?
  • Push some other product that creates another, yet unneeded GraphQL layer (whatever Hypermode was using)?

J

Hi Jonathan, Thanks for the welcome message.
Maggie’s team (Engineering) is working on the roadmap for 2026 so we should soon clarify how Dgraph will fit in Istari Digital platform.

What is clear now

  • we want Dgraph to be a maintained open source project by its own.
    We have moved all repositories back to dgraph-io, we are working to get the dgraph.io domain transferred to us, so we can reconfigure routes.
    @matthewmcneely is working on the CI/CD. Setting up runnners, credentials to push on dockerhub, dependencies etc …
    I’m working at cleaning the doc from marketing and unrelated info to get only Dgraph doc and improve it to help community to host Dgraph and to contribute to the project more effectively.
    The online doc is still at docs.hypermode.com at the moment.
    We should be back on dgraph.io when we get the domain.
    You can access the doc I’m wokring on at https://dgraph-docs.pages.dev/ (it will be docs.dgraph.io asap). I’m planning to put more explanations about the code itself (lot of stuff I got from Dgraph/Hypermode). The admin part and hosting guide is messy. The Hypermode section has a lot about migrating from Cloud which is not a topic anymore. I started to re-organize the admin section. If anyone has good content about operations, please contribute to GitHub - dgraph-io/dgraph-docs: A native GraphQL Database with a graph backend

  • new features initiated by Istari Digital will be driven by our customers and our own usage of Dgraph.
    You can expect work on security, scalability and distribution. The unique approach of predicate sharding is of high interest.
    We will work on the query language too. It is a bit to soon to decide on which languages must be supported for our customers (gremlin, openCypher, GQL?). There is an option to document and open the internal representation in Dgraph so people can contribute and add languages.

  • GraphQL: we are focusing on Dgraph as distributed graph database. At the moment I see the evolution of GraphQL as a community effort but it could change if we have interest in that domain from our customers.

Hope it brings a bit of clarity. Will share more as I get more understanding on my side.
-R

Ok nice.

My opinion, at this point I think it is smart to separate GraphQL layer and focus on Dgraph as a Graph database… plenty of needed features there in DQL.

Will the cloud hosting come back?

Thanks,

J

1 Like

I started to separate GraphQL from the core DB in the doc :slight_smile:
No plan for cloud hosting on Istari side.
If you have DevOps / Hosting related docs to share you can also send that to me and I’ll see how to include it in the doc.
I have some material on my side ( GitHub - rderbier/infra: test render infra for Modus Dgraph and Embedding service. ) for Dgraph on Render for example that I’d like to include in a way. We need to help people hosting Dgraph, grow the community to get more contributors !

Thanks.

I’m honestly never going to self host it, as I’m not a engineer. I never used Dgraph until the Cloud was released. I also never used Modus for the same reason. I don’t want to host another layer outside of my TS backend.

I don’t know if I can help much. I hope it does well for that community though

J

I totally agree about focusing on Dgraph as a Graph database. There’s a lot to be offered and used when looking at Dgraph as a pure graph database.

2 Likes

I‘d be really happy if you‘d bring dgraph cloud back alive

Self Hosting this is way too hard

maybe you can team up with fly

I have made a forum post there

Will Fly offer Dgraph support? - Fly.io

1 Like