Reputo on the toolkit: what came on day one, and what we built

Reputo is for the marketing lead of a small business that sends its own campaigns. It says, in plain language, whether the company's email is arriving, what is wrong, and what to ask IT to change. It runs in a dev environment and is not in production yet.

Behind those answers sits a multi-tenant SaaS: organizations, members, plans, usage limits, an admin interface for the operator. A buyer pays for none of it, and all of it has to work before the first customer signs in.

Day one: the toolkit

Reputo's first commit, on 20 September 2026, held a domain-check core, rebuilt from earlier work, and a vendored copy of our toolkit. The same morning, the API ran against a real PostgreSQL database and listed 42 routes. Thirty-four came from the toolkit: onboarding, organizations, entitlements, usage, billing and admin. Of the 12 tables in the first migration, 11 were the toolkit's.

Reputo's AppDbContext derives from the toolkit's OrganizationDbContextBase, so every entity that belongs to an organization gets a tenant filter, and Reputo's queries over monitored domains rely on it. On the SaaS side, Reputo's own code that day was the wiring in Program.cs and its plans: Free, Pro and Business with their quotas, and a hook that gives each new organization the Free plan.

Twelve days: the product

The next twelve days went into Reputo's own code around that core: DMARC aggregate reports collected from a mailbox, per receiving provider; incidents with alert mail in Slovenian; integrations with Google Postmaster and Microsoft SNDS; and the screens. On 2 October main was first deployed to a dev environment. Keycloak did not start on the first attempt; the second, under half an hour later, passed the checks of the API, the app and the Keycloak realm.

For a team starting a product on the toolkit, the measure is where the first weeks go. In Reputo, tenancy, members, entitlements, usage limits and the admin endpoints were wired into the API on the first morning, and the twelve days to a dev environment went into the checks, reports and alerts its buyer would pay for.