Services
Custom software developmentUmbraco developmentWeb developmentCRM developmentERP developmentAI & LLM integration.NET development & modernizationE-commerce developmentIntegrations & automationCloud & DevOpsMaintenance, support & project rescueDedicated teams & white-label
Our Work
Case studiesProducts
About Blog Contact
GraphQL development

GraphQL APIs on .NET, and GraphQL data in your CMS.

We have worked with GraphQL from both sides: building a HotChocolate GraphQL API for a large .NET business portal, and consuming a GraphQL API to keep property listings in sync across several Umbraco websites.

What we build with GraphQL

Where GraphQL earns its place.

The kinds of work we use GraphQL for, based on the projects below rather than a list of everything the technology can do.

GraphQL APIs on .NET

HotChocolate schemas over Entity Framework and SQL Server, so front ends ask for exactly the data a screen needs.

GraphQL imports into a CMS

Configurable mapping from GraphQL fields to CMS properties, with parallel imports, media handling and history of every run.

Gateways over existing systems

A single typed API in front of several services, so mobile and web clients do not need to know where data lives.

GraphQL FAQ

GraphQL questions we hear.

Anything missing? Send us your question and an engineer will answer, usually within one business day.

Contact us
Should we use GraphQL or REST?+

GraphQL pays off when many different screens or clients need different shapes of the same data. For simple integrations and webhooks REST is easier to run. We often use both in one system.

Which GraphQL server do you use on .NET?+

HotChocolate. We used it on the HS High Stake business portal alongside Entity Framework, SQL Server and Elasticsearch.

Can you import data from a GraphQL API into Umbraco?+

Yes. Our importer pulls property data from a GraphQL API into any Umbraco site, maps it by configuration and runs in parallel. It is reused across sites by adding one DLL reference.

Start a project

Tell us what you are building with GraphQL. We come back with a plan and a price.

A spec, a Figma file or three paragraphs is enough to start.

  1. First reply · from an engineer, not a sales rep
  2. 30-min call · with Roman, our CTO, to clarify scope
  3. After the call · a written proposal with plan, team and price
Roman Oleksuk
Roman Oleksuk, CTOPrefer to talk? Pick a slot in Roman's calendar
We reply from a human mailbox. No newsletters. Your brief stays under NDA on request. We use your details only to reply; see our privacy policy.