Web apps in .NET and Blazor
Business systems, admin dashboards and portals in ASP.NET Core and Blazor, with a clear architecture that stays easy to extend.
Software house · Katowice, Poland · .NET, Blazor, Rust
Artisso designs and builds software for businesses: web apps in .NET and Blazor, integrations with external services, mobile apps and AI features. And to know our tools inside out, we also build our own operating system.
Our code is public. Check us out on GitHub.
// Blazor + two of our open-source libraries
using Blazor.Component.Maps;
using Blazor.Identity.UI.Extensions;
var builder = WebApplication.CreateBuilder(args);
builder.Services.AddMapsServices();
builder.Services.AddSingleton<IEmailService, EmailService>();
var app = builder.Build();
app.UseBlazorIdentityUI();
app.Run();
$ dotnet run
info: Now listening on: https://localhost:5001
Figures from GitHub, NuGet and the OSAIKU repository, October 2026.
01 — Services
Most of our work lives in the .NET ecosystem, but we do not stop at the application layer. When a project needs it, we go down into integrations, databases, mobile devices and the operating system itself.
Business systems, admin dashboards and portals in ASP.NET Core and Blazor, with a clear architecture that stays easy to extend.
ASP.NET Core Identity shaped to your project: sign-in screens as Blazor components, custom user stores, roles and permissions.
We connect your system to the outside world: Google Maps and Places, Poland's REGON business registry (BIR), third-party REST and SOAP services, and your own APIs.
Android and iOS apps in the .NET ecosystem, connected to your backend. Our Xamarin.Forms plugin has more than 5,000 downloads.
Kernels, drivers, filesystems and UEFI boot. We build our own operating system, so low-level work does not scare us.
Agents and language models wired in safely: typed actions, clear permission boundaries and human approval instead of magic.
02 — How we work
Artisso is a software house from Katowice, Poland. There are no layers of middlemen: the engineers who gather your requirements are the same ones who design the architecture and write the code, so nothing gets lost along the way.
We work in short iterations and show you working software after each one, not slides. You make the call on every important step. It is the same rule we built OSAIKU around: a person approves, the machine executes.
How a project runs
03 — Flagship project
The best proof of skill is working code. OSAIKU is our research and development project: an experimental x86_64 UEFI operating system where people and AI agents work together safely, through typed, bounded and human-approved actions.
04 — Open source
We release some of our tools as open libraries. It is the quickest way to judge how we write code.
Google Maps and Google Places autocomplete for Blazor apps, with extra support for MudBlazor.
Replaces the Razor pages of Microsoft.AspNetCore.Identity.UI with native Blazor components in a separate library.
A client for the BIR 1.1 service of Poland's REGON business registry, for .NET Standard 2.0 and .NET Core. Look up companies by NIP and REGON.
ASP.NET Core Identity backed by Dapper instead of Entity Framework. Works with .NET Core and Blazor.
A customisable date and time picker for Xamarin.Forms mobile apps.
A Unity plugin that automates building in-game tutorials: dialog windows, overlays and a step editor.
05 — Stack
We specialise in .NET, and the same team writes an operating system in Rust. We choose what solves your problem best and what your team can maintain after us.
06 — Contact
Write a few sentences about what you want to build, or what is not working in your current system. We will reply with questions and a proposal for next steps.