Pilot programme — Demo available now

Regulatory submissions shouldn’t take months.

RegPro gives medical device regulatory affairs teams AI-powered authoring tools — built to the same standard as the submissions they prepare.

Local-first · Zero cloud storage
21 CFR Part 11 audit trail
FDA · EU MDR · Health Canada
Built for submissions to
FDA 510(k) · De Novo · PMA EU MDR 2017/745 Health Canada MDL TGA · PMDA · ANVISA
The problem

Generic AI tools weren’t built for regulated submissions.

Medical device regulatory work has rules that general AI doesn’t respect — jurisdictions, audit trails, traceability, and the kind of citations that hold up under inspection.

Submissions take too long

A single Class IIa device targeting FDA + EU MDR requires 7–12 documents. Most of that time is spent on structure, formatting, and figuring out which standard applies to which jurisdiction.

Generic AI creates liability

General-purpose assistants hallucinate regulatory citations, ignore jurisdiction differences, and generate outputs with no audit trail — making every output a liability, not an asset.

Knowledge walks out the door

When your senior RA lead leaves, their prompt library, their templates, and their submission patterns go with them — and the next hire starts from scratch.

How it works

From device profile to filed document — in a fraction of the time.

RegPro keeps your device context, your prompts, and your audit trail in one place — on your machine.

01

Create a device profile

Tell RegPro your device class, intended use, and target jurisdictions. RegPro immediately shows you every document your submission requires.

// FDA + EU MDR + HC → 11 documents
02

Select & assemble prompts

Choose from an expert-curated prompt library or create your own. RegPro injects your device context and redacts PII automatically.

// curated library · multi-provider · PII safe
03

Generate, review & trace

Run against your chosen AI provider. Review the draft. Accept — and RegPro saves the output with full traceability to the prompt version that produced it.

// HMAC-SHA256 hash chain · tamper-evident
Capabilities

Six capabilities that separate RegPro from a chat window.

Every feature exists because a regulatory professional asked for it — not because it looked good in a deck.

Local-first privacy

Device data, API keys, and audit logs never leave your workstation. DPAPI encrypted at rest. Zero cloud storage of sensitive device information.

DPAPI · AES-256

Jurisdiction intelligence

Input device class + target markets. RegPro maps your configuration to the exact submission documents required across FDA, EU MDR, Health Canada, TGA, and more.

FDA · EU MDR · HC · TGA

Expert prompt library

A growing library of expert-authored prompts curated by a former Notified Body assessor — risk management, clinical evaluation, cybersecurity, usability engineering, software lifecycle. Add your own custom prompts to fit your device and workflow.

curated · extensible · versioned

21 CFR Part 11 audit trail

Every action is HMAC-SHA256 hash-chained and tamper-evident. Every output is attributed to the exact prompt version and user that produced it.

HMAC-SHA256 · immutable

Multi-provider, BYO keys

Bring your own API keys for Anthropic Claude, OpenAI, Azure OpenAI, Google Gemini, DeepSeek, xAI Grok, Perplexity, local Ollama, and more. Choose the model for every task. New providers added as the field evolves.

BYO keys · per-task model

Bidirectional traceability

User need → requirement → design → code → test → risk. Maintained as a first-class product feature. Every prompt version is preserved. Nothing is ever deleted.

UR → REQ → DES → TEST
AI providers

Bring your own keys. Pick the right model for the job.

RegPro doesn’t lock you into one provider — or charge you a markup on tokens.

A Anthropic Claude
G OpenAI GPT
Az Azure OpenAI
Gm Google Gemini
DS DeepSeek
xA xAI Grok
Px Perplexity
Ol Ollama (local)

More providers added as the field evolves — AWS Bedrock, Google Vertex AI, Mistral, and others on the roadmap.

Built to the standard

RegPro is developed to the same standards it helps you comply with.

We don’t just help you prepare IEC 62304 submissions. RegPro itself is developed under IEC 62304 Class A, with full ISO 14971 risk management, IEC 62366-1 usability engineering, and 21 CFR Part 11 electronic records compliance.

IEC 62304Class A · 2006+A1:2015
ISO 14971:2019Living hazard register
IEC 62366-12015+A1:2020
IEC 81001-5-1Cybersecurity, 2021
21 CFR Part 11Electronic records
EU MDR 2017/745GSPR §17
GDPRArt. 25 & 32
HIPAA§164.312
WCAG 2.1 AADesign target
Rajeev Yadav, Ph.D. — Founder, TeckFile Inc.
Founder

Rajeev Yadav, Ph.D.

Founder, TeckFile Inc.

“I spent years reviewing medical device submissions as a Notified Body Technical & Clinical Assessor. I saw the same avoidable mistakes slow down life-saving products over and over — not because the teams weren’t capable, but because they lacked tools built for the regulatory context. RegPro is the tool I wished existed.”

FormerNotified Body Technical & Clinical Assessor (2023–2025)
FormerDirector R&D, ODS Medical (2015–2023)
PatentsJP7257009B2 · US12433488B2
ExpertiseIEC 62304 · ISO 14971 · EU MDR · FDA 510(k) · IEC 62366-1 · IEC 81001-5-1
Limited cohort

Join the pilot programme.

RegPro is currently in private beta. We’re onboarding a small number of medical device manufacturers and contract RA firms. Pilot participants get early access, direct input into the product roadmap, and preferred pricing at general availability.

Apply for Pilot Access

Or email us directly at info@teckfile.com