history_edu Case Study · Open-source product

Inkwell: Open-Source Multi-Tenant Blogging Platform on .NET

A self-hosted blog and CMS that serves many sites from one installation, with every line of its source code, its test suite and its release history public on GitHub.

  • category Publishing & Media
  • public Global (open source)

By the PixoBots engineering team · Last updated

At a glance

11

Tagged releases between May and October 2026

817

Automated xUnit test methods in the public repo

20 × 16

Layouts × colour Presets: 320 combinations

MIT

Licence: free to self-host and modify

report_problem 01

The Challenge

Teams that run their business on .NET and SQL Server often end up with a PHP blog bolted onto the side of their stack, or a hosted platform where pricing, export and data residency are out of their hands. Agencies that manage several client sites face a multiplied version of the same problem: one installation, one database and one patching routine per site.

Inkwell was built to answer both. The brief was a blog and website CMS that a .NET team can host, read and extend without learning a new ecosystem, that can serve many separate sites from a single deployment, and that collects no telemetry. Because it is open source, it also had to hold up to public code review from day one.

construction 02

The Solution

PixoBots designed and built Inkwell, and publishes it under Maruti Software Solutions, PixoBots' registered business name. We also provide installation, support and custom themes for it. It is an ASP.NET Core MVC application on .NET 10 with a Dapper and raw-SQL data layer over Microsoft SQL Server. Pages are rendered on the server as plain HTML, which keeps them fast and easy for search engines to read. The database schema applies itself on startup, so an upgrade is a redeploy rather than a migration project.

Multi-tenancy is a configuration switch: in Cloud deployment mode, one installed binary hosts many sites, each isolated by its URL slug with its own authors, Layout and Preset. Posts and pages share one editor, and pages get a drag-and-drop block builder, so a client's About, Services and landing pages live in the same system as the blog.

The repository is the proof. The test suite lives next to the code, each release is tagged with dated notes in the changelog, and a GitHub Actions workflow builds the Docker image and boots the full stack on an empty database on every push, so the documented install is verified by running it.

What we built

  • Multi-tenant hosting from a single deployment
  • WYSIWYG or Markdown editor for posts and pages
  • Drag-and-drop page builder with a Form block
  • Header and footer menus managed by content ID
  • 20 editorial Layouts and 16 colour Presets
  • SEO tooling: structured-data checks, IndexNow, redirects
  • Built-in analytics, including AI-crawler reports
  • Docker Compose deployment, verified in CI
layers 03

Tech Stack

  • .NET 10
  • ASP.NET Core MVC
  • C#
  • Dapper
  • Microsoft SQL Server
  • Razor
  • Docker
  • GitHub Actions
  • xUnit
trending_up 04

The Results

  • 11 tagged releases from v1.0.0 (15 May 2026) to v1.0.10 (28 October 2026), each with dated release notes.
  • 817 automated xUnit test methods in the public repository, run as part of the development workflow.
  • Every push and pull request boots the Docker Compose stack on an empty database in GitHub Actions, catching deployment regressions before release.
  • 5 GitHub stars and 3 forks as of November 2026.
  • Two sites run on Inkwell today: a public demo site and opticalsoftware.org.
  • Buyers evaluating PixoBots can read the code, the tests and the commit history directly instead of relying on a portfolio screenshot.

Have a similar project?

Tell us what you need to build. We reply within 24 hours and sign an NDA before any details are shared. You own the code and IP.