[mlukaszczyk]

Hey! I'm one of the co-founders of GraphCMS.

We will soon start open sourcing our content management interface, so users have the opportunity to customize the CMS UI to their needs. Most of our customers just want us to take care of the hosting.

[everdev]

Yes, I'd be interested if I could self-host. As others mentioned, having this externally hosted introduces another potential point of failure.

[CharlesW]

> We will soon start open sourcing our content management interface, so users have the opportunity to customize the CMS UI to their needs.

"We're going to open source the interface" is a disingenuous answer to the question. Documenting an interface isn't open source. If your plan is "proprietary SaaS", just own it.

[j45]

+1 Very interested in self hosting. Especially to meet data residency and locality requirements for a few projects that I have.

[neeksHN]

+1, very much looking forward to that Show HN.

[tcc8]

Can you compare pros/cons to Contentful?

[mlukaszczyk]

GraphCMS is the only CMS that exclusively offers GraphQL. Other CMSs have since entered the space to offer GraphQL technology, but they still try to maintain both REST and GraphQL APIs which will lead to some maintenance issues in the future. An example of this is that the other CMSs aren’t able to offer a “mutation” API for their CMS through GraphQL. With our CMS you can query the data and change it through the same powerful interface. This opens the door to a wide range of tooling and custom workflow enhancements. Additionally, because we only offer GraphQL, we are able to be more agile with changes to the technology.

In the future, our focus will shift even more to content based BaaS as we will support end user authentication. We are also preparing a new suite of workflow tools that will make managing large datasets a breeze.