GraphQL APIs on .NET
HotChocolate schemas over Entity Framework and SQL Server, so front ends ask for exactly the data a screen needs.
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.
The kinds of work we use GraphQL for, based on the projects below rather than a list of everything the technology can do.
HotChocolate schemas over Entity Framework and SQL Server, so front ends ask for exactly the data a screen needs.
Configurable mapping from GraphQL fields to CMS properties, with parallel imports, media handling and history of every run.
A single typed API in front of several services, so mobile and web clients do not need to know where data lives.
Which part of the system it ran, and what it worked with. Every row links to the full case study.
Each one with the client’s problem, our approach and what changed.

A service and DLL pair that pulls property data from a GraphQL API into any Umbraco site, maps it by configuration and imports it in parallel.
OSKI developers joined HS High Stake to build modules for a large business portal that links a German division, its dealers and its employees.
We do not sell hours of a technology. We take on a result, and choose the stack with you. These are the services where GraphQL usually comes in.
Each one backed by at least one published client project.
Anything missing? Send us your question and an engineer will answer, usually within one business day.
Contact usGraphQL 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.
HotChocolate. We used it on the HS High Stake business portal alongside Entity Framework, SQL Server and Elasticsearch.
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.
A spec, a Figma file or three paragraphs is enough to start.

Cookies on oski.solutions
We'd like to use analytics cookies to understand how the site is used, and marketing cookies to measure our ads. They are off unless you allow them. You can change your choice any time via “Cookie settings” in the footer. Cookie policy