Skip to main content

About

An infrastructure company.

Regain, Inc. is a Delaware C-Corporation building clinical AI infrastructure for healthcare accreditation. Self-funded. Field experience deploying clinical systems at medical centers in Central Asia. Building toward HIPAA compliance with engineered separation of PHI and PII. Early in an industry transformation that will take years to complete.1

Two-org structure, one substrate: Regain, Inc. for US business and BAA-covered workloads; Salomatic, LLC as the engineering cost center where the team is based. Read the sections →

Figure 1.1

One substrate, three layers

Editorial diagram titled ONE SUBSTRATE THREE LAYERS, three labeled tiers (reviewer surface, compliance evaluation, clinical data pipeline) stacked vertically, with a single hairline marking ONE DATABASE / ONE AUDIT TRAIL through all three. Tabular small-caps annotations on the right.
Reviewer surface, compliance evaluation, and the clinical data pipeline share one database, one audit trail, one deployment. Compliance evaluation lives next to the clinical data it measures, not downstream of it.2

By the numbers

Company facts.

Founded

2023

Delaware C-Corporation

Self-funded. No venture capital. No board seats held by investors optimizing for metrics that conflict with reliable healthcare infrastructure.

Headquarters

US · UZ

Two-org structure

Regain, Inc. (Delaware) for US business and BAA-covered workloads; Salomatic, LLC (Tashkent) as the engineering cost center where the team is based.

Field experience

Central Asia

Clinical systems deployed

Field experience deploying clinical systems at medical centers in Central Asia. The engine is sandbox-tested against published standards frameworks; live accreditation customers are the next milestone.

How we operate

Four operating commitments.

Healthcare infrastructure runs on the deployment timeline, not the fundraising one. Four commitments shape every architectural decision and every customer engagement.

  1. 01

    Self-funded

    No venture capital. The company exists on the customer timeline, validated through pilots, earned through institutional trust.

  2. 02

    One shared substrate

    Clinical data, compliance evaluation, and the reviewer surface share one database, one audit trail, one deployment. Compliance lives next to the data it measures.

  3. 03

    Defensibility-first

    Every claim must survive an audit. The trust model is built into the architecture, not the certification roadmap. Determinism, hashing, RBAC, provenance.

  4. 04

    Open where it matters

    Communication and supervision protocols planned for Apache 2.0 release. Trust is verifiable from outside the company, not just from inside it.

Read more

Sections of this page.

Team

The people building the platform, clinical, scientific, and engineering leadership.

Meet the team →

Careers

Open positions in regulatory, clinical integration, and AI research. Pipeline roles open now.

View open positions →

Epistemology

How we know what we know. The Popperian foundation behind every clinical AI claim and every supervision verdict.

Read the approach →

Hard to Vary

A deeper dive into the epistemological standard we apply to clinical reasoning, explanations that resist alteration without breaking the explanation.

Hard to Vary deep dive →

Privacy & Security

How we handle clinical data. Engineered separation of PHI and PII, building toward HIPAA compliance, and our security posture.

Privacy policy →

Self-funded

Healthcare infrastructure runs on the deployment timeline, not the fundraising one.

Regain is self-funded. No venture capital. No board seats held by investors optimizing for growth metrics that conflict with building reliable healthcare infrastructure. Healthcare institutions adopt on a timeline measured in years, validated through pilots, earned through institutional trust. We chose that timeline.

Figure 3.1, Two entities, one engineering substrate

Single-substrate architecture diagram showing the engineering layers, editorial marginalia titled INFRASTRUCTURE COMPANY, two concentric vertical columns labeled Regain Inc. (Delaware) and Salomatic LLC (Tashkent), with a horizontal shared-substrate line crossing both. Below: five small dots labeled CEO/CTO/CSD/QA/QA. Hairline navy linework on cream paper, single muted-teal accent.

Figure 4.1

Infrastructure company architecture

Editorial topology diagram titled INFRASTRUCTURE COMPANY ARCHITECTURE, three concentric stacked layers (data substrate, compliance evaluation, intelligence surface) with a single vertical hairline labeled ONE AUDIT TRAIL piercing all three, plus three lateral annotations: shared database, shared RBAC, shared deployment.
Self-funded means engineering effort is concentrated on the substrate, not on growth instrumentation. Every team member contributes to one shared stack.

Read more

Adjacent sections.

Use Cases

How the platform serves accreditors, facilities, clinical programs, and international health systems on a single substrate.

Explore Use Cases →

Insights

Long-form analysis on the structural forces reshaping accreditation, visibility gaps, manual abstraction costs, voluntary erosion, AI governance.

Read the Insights →

Trust

Security architecture, deterministic evaluation, HIPAA posture, and open standards, the engineering decisions that make the platform auditable.

See the trust architecture →

Talk to the people building the platform.

We will walk through your accreditation context and show how a shared evidence substrate changes what becomes possible.

Request a demo

Footnotes

  1. Regain, Inc. (US Delaware C-Corporation, EIN 36-5080480), operating headquarters in Tashkent, Uzbekistan via Salomatic, LLC (UZ INN 310822815). The two-org structure is intentional, not a transition.
  2. Same five-person team serves both entities. Engineering and product run on a single shared engineering substrate; the entity split applies only to revenue, payroll, and regulatory surface.