Built by engineers who understand regulated industries.

OwnAI is built by Reyatech Systems Private Limited — a small, focused team that ships.

§2 · Founder

The person on the other end of every email.

Headshot placeholder · 1:1 · 800×800
Founder & CEO

Rishi TodeFounder & CEO · Reyatech Systems Private Limited

11+ yrs · VLSI / IP verification ex-Synopsys SystemVerilog / UVM I3C · SAS · Fiber Channel

15 years in IP / VLSI verification engineering. Synopsys background. Built protocol verification IP for I3C, SAS, and Fiber Channel across multiple silicon vendors. SystemVerilog / UVM specialist.

Founded Reyatech Systems Private Limited after watching semiconductor and pharma clients struggle with the same problem: AI capability they couldn't deploy because of data sensitivity and licence flow-down complexity.

§3 · Why this exists

Three observations. One company.

01

Indian enterprises need AI. They can't send regulated data to US servers.

02

Per-seat AI bills don't stop. Enterprises deserve to own their AI.

03

Open-source models are now production-ready. The gap isn't capability — it's deployment.

§4 · Operating principles

Three pillars. Non-negotiable on every engagement.

Pillar 01

Data Sovereignty

Your data, your hardware, your premises. Always. No "we hold a copy for ops." No "telemetry helps us improve." None of that exists in production.

Pillar 02

Cost Ownership

One-time investment, not perpetual rent. The shape of the contract matches the shape of the asset — you own the system, you fund the build, you control the lifecycle.

Pillar 03

Open Source First

Apache 2.0 / MIT base models. No vendor lock-in. You own the weights, the adapter, and the source. The stack is replaceable, top to bottom.

§5 · Continuity — said out loud

What happens if Rishi Tode gets hit by a bus?

We've engineered against single-person dependency from Day 1. Five mechanical guarantees protect you — none of them require us to still exist.

  1. Source-code escrow on Day 1.
    With a neutral third party (e.g. NCC Group / Iron Mountain). If we ceased to operate, you receive the full codebase under your existing SOW.
  2. Apache 2.0 / MIT base models.
    The models that power your system are not ours; they belong to the open-source world. Qwen 3, DeepSeek-R1-Distill, Phi-4 don't depend on Reyatech existing.
  3. Adapter weights are yours.
    Under §7 of every SOW. The fine-tune is the customer's IP from delivery. Permanent, transferable, irrevocable.
  4. 100% open-source stack.
    Ollama, vLLM, LiteLLM, Qdrant, Langfuse, Keycloak. Any qualified vendor or your internal team can take it over. No closed-source artefacts in production.
  5. Runbook ships with every engagement.
    No tribal knowledge required to operate the system. Deploy, refresh, restore — every step documented in the handover dossier.

In short: even if Reyatech disappeared tomorrow, your AI keeps running — because nothing it depends on lives behind our door.

§6 · Company

The entity. The registry. Verifiable.

Legal name Reyatech Systems Private Limited
CIN U62013KA2025PTC212560
Registered office HRBR, Bangalore, Karnataka – 560043, India
Incorporation 16 Dec 2025
Founded 2025
Capital structure Bootstrapped · customer-funded

Bootstrapped. Customer-funded. No external investors.

Reyatech Systems is funded entirely by founder capital and customer revenue. There is no VC clock pressuring us to ship features that look impressive in board decks but degrade your security posture.

Aligned with the customer. The roadmap is set by paying customers, not by the next funding round.
§7 · Roadmap

Quarterly checkpoints. Refreshed each quarter.

Today is May 2026. Roadmap dates render from a single source of truth so they never go stale silently.

  1. 2026-Q2 · NOW

    Pharma GMP and NBFC pilots · Layer-1 runtime PoC in customer environments

    First six pilots underway in discovery. Layer-1 deployment runtime validated on Mac Mini, 4090 workstation, and L40S server. Eval rubrics signed on every pilot.

  2. 2026-Q3

    First two production deployments live · AMC pilots begin

    Production go-live on the first two engagements. Anonymised case studies publish. AMC v1 onboarding for the production cohort.

  3. 2026-Q4

    Third production deployment · SOC 2 readiness assessment kicks off

    Third production rollout. ISO 27001 and SOC 2 readiness assessments begin in parallel — tracked alongside customer deployments.

  4. 2027-Q1

    Vertical pack v2 (additional pharma use cases) · first NBFC production deployment

    Second-generation pharma pack with audit-prep, change-control, stability-summary modules. First NBFC production go-live.

  5. 2027-Q2 · BINDING

    DPDPA Phase-3 binding (13 May 2027)

    Full Phase-3 operating posture in place across all customers — DPO appointed, breach-notification workflows live, retention configurable per data class.

  6. 2027-Q3

    SOC 2 Type II attestation target

    Type II attestation report target. ISO 27001 stage-2 audit in parallel.

We ship quarterly. Every AMC customer gets model refreshes — new Qwen / DeepSeek / Phi releases evaluated and migrated within one quarter of upstream GA.

§8 · Advisors

Advisors and references.

Advisor roster announces after Q3.

Initial advisors are operating under NDA while their organisations finalise public disclosure. Drop us a line if you're a regulated-industry leader who wants early access to the product roadmap.

Next step

Want to work with us? Let's talk.

A 30-minute call with the founder. No SDRs, no funnel — your first email lands on the same inbox that signs your SOW.

rishi@reyatech.com +91‑7486461783