Our own products

Remedy Lab, BrightPages, and the products we build for ourselves.

Client work pays the bills; our own products keep us honest. Everything we ask a client to trust us with — architecture, store compliance, AI guardrails, release engineering — we do first on software with our own name on it.

Available on Google Play iOS in development

Remedy Lab

Ask a question in plain language. Get clear, step-by-step instructions for natural remedies and homemade products — with hazard screening on every single response.

Remedy Lab is an AI-native mobile application built with .NET MAUI. The distinguishing feature isn't the AI; it's what surrounds it. Every response passes through automated hazard screening and explicit refusal handling before a user ever sees it, because "mostly safe instructions" is not a standard anyone should ship.

Remedy Lab

"Something soothing for a sore throat?"

Instructions

01Warm 8 oz of water — not boiling.
02Stir in 1 tsp honey until dissolved.
03Add 2 tsp fresh lemon juice.
04Sip slowly. Repeat up to 3× daily.
Safety check

Not for children under 1 year — honey carries a botulism risk in infants.

Under the hood

Why this app is our best sales pitch.

Remedy Lab is a working demonstration of how we think AI products should be engineered. Everything below is shipping, not aspirational.

The AI runs on your phone

By default, inference happens on the device itself. No round trip to a server, no per-query cost, and no user data leaving the handset. The app works in full with no signal at all — which for a product people reach for in a kitchen or a cabin is the point.

Guardrails in every response

Automated hazard screening and explicit refusal handling are part of the response pipeline, not a disclaimer in the settings screen. When the safe answer is "don't do this," the app says so plainly instead of improvising.

One schema, three engines

A single response contract is served interchangeably by an on-device model, a model hosted on a local network, or a cloud provider. Swapping engines is configuration, not a rewrite — the same architecture we build into client systems.

Held to a hard engineering bar

Layered architecture enforced by automated architecture tests, a standing 90% code-coverage gate, zero-warning builds, and full CI/CD through signed, store-ready release packaging. The build fails before a bad design ships.

Built with

.NET MAUI MVVM On-device LLM inference Local network inference Cloud inference SQLite GitHub Actions CI/CD Architecture tests Store-managed subscriptions

Platforms

  • Android Available now on Google Play.
  • Windows Built from the same codebase.
  • iOS In development.
In development E-commerce platform

BrightPages

Online stores for businesses of every size, from a one-person shop to a multi-brand enterprise, engineered like an enterprise system and simple enough to set up in an afternoon.

BrightPages is our newest product and our largest: a multi-tenant e-commerce platform R&T BrightLight is writing from the ground up. It is designed so that every store gets the commerce essentials, and a business switches on add-ons as it grows, with no migration and no downtime. Merchants will make a store their own with starter templates, a visual editor that previews every change as it is made, and an AI assistant that helps with the writing and the design.

Stores will be able to join organizations that share branding and content, so a business with several brands or locations can keep them consistent without keeping them in sync by hand. Every store will get its own address on day one and can bring its own domain, with the security certificate handled for it.

Planned for every store

  • Sell Product catalog, cart and checkout, discounts and promotions.
  • Fulfill Orders, shipping, and sales tax.
  • Stay in touch Customer contacts and order notifications.
  • Reach further Product feeds to the marketplaces and channels your customers already use.

Planned add-ons

AI assistant Inventory Analytics Appointment booking Reviews Email & SMS marketing Gift cards Subscriptions Loyalty & referrals Wholesale Website pages

Secure by design

A store platform built to the standard we hold ourselves to.

A platform that holds other businesses' customers, orders, and payments has to be secure from the first line of code. BrightPages is still in development, so this is how it is designed rather than a list of features you can use today.

Every store stands alone

Each store is isolated from every other: its customers, orders, staff, and private data are never visible to another store. Stores share branding or content only when their owners group them into an organization, and automated tests prove the isolation on every change instead of assuming it.

Card numbers never touch it

Checkout uses payment fields hosted by the payment provider, so card details go straight to the processor and never reach BrightPages. Merchants keep the lightest possible card-security compliance burden.

The right access for each person

Merchant sign-in supports multi-factor authentication and passkeys, and staff roles give each person only what their job needs. Our own support staff can reach a store only with the owner's approval, for a limited time, and every visit is recorded.

An AI assistant that asks first

The AI assistant drafts changes for the merchant to review, and nothing goes live without their say-so. It sees only the store it is working in, acts only with the permissions of the person using it, and is never given passwords or keys.

Engineering bar

Infrastructure as code Zero-downtime releases Instant rollback 90% coverage gate Zero-warning builds Vetted, pinned dependencies Accessible storefronts (WCAG 2.2 AA)

Built for

  • Small businesses A complete store without hiring a developer.
  • Growing brands Add capabilities as you need them, on the same store.
  • Enterprises Many stores under one organization, kept consistent.

What this means for you

Nothing we propose is theoretical.

When we recommend on-device inference, a provider-agnostic layer, or a coverage gate, we're describing something we already operate — including the parts that were harder than expected.

It also means our estimates account for the whole job. Store review cycles, signing certificates, subscription restore behavior, and privacy declarations are in the plan from the start, because we've paid for underestimating them ourselves.

More on the way

Our product line is growing.

We maintain Remedy Lab actively, BrightPages is in development, and more is planned. If you'd like to hear when something new ships — or want to talk about building your own — get in touch.

Next step

Want an app built to this standard?

Tell us what it should do and who it's for. We'll come back with a realistic scope and an honest read on what it takes to keep it alive after launch.