Hosted Slash Graphql deployment configuration

I am looking at using Slash Graphql to host dgraph for a project I’m working on. I’ve been told that Slash Graphql instances are single nodes, with no replication. Is there any documentation that explains how the service is resilient to failure? Also how does the service automatically scale with increasing amounts of data?

I think @gja can help to clarify this.

Thanks for the question. We currently are only supporting single node dgraph instances, though we are working on models for replication.

We are storing all data on individual ebs volumes so that even if your dgraph instance crashes or is migrated to another box, your data remains intact.

Please contact our sales team / @dereksfoster99 so that we can better understand your use case