सायुज्य · About Sayuk
Deep union. Inseparable connection.
Sayuk comes from the Sanskrit root sayujya (सायुज्य) — a Vedantic word for the state of inseparable union, the bond between two things that are no longer separate. We chose it because that is what we build: a software layer where one person's identity, places, family and choices stay together across every product they use.
01 / Why the name matters
Most platforms collect you.
We connect you.
Every Indian uses a dozen apps daily — clinic, bank, market, filing, savings. Each one keeps its own login, its own profile, its own opinion about who you are. A dozen profiles of one person, scattered, never reconciled.
Sayuk inverts that. One identity. One family graph. One address book. One consent ledger. Products don't own your data — they read from one canonical layer you control. That is the union the name points to.
Sayujya isn't possession. It's the state where two become one without either being lost — the only honest framing for what software should do with your data.
02 / What we're building
Seven products.
One account.
Two are built for the businesses that run India — software for the desk, not the deck. Five are built for the person who lives in it. Each one carries its true state.
For the businesses that run India
- Sayuk Tend Shipping
Clinic + GST pharmacy on one ledger. Reception, doctor and counter write to the same database. Live in a real hospital.
- Sayuk Edge Live
A systematic F&O stack, trading our own capital on real money since 6 May 2026.
For the person who lives in it
- Sayuk Tax Live
Free ITR filing — a Zerodha .xlsx becomes classified capital gains and a valid ITR-1, ITR-2 or ITR-3 XML.
- Sayuk Pact Alpha
Savings circles and a trip splitter. Tracks the math, never touches the money.
- Sayuk Shield Alpha
Family health vault, shared per-relation by consent, with a DPDP audit trail.
- Sayuk Trove Alpha
Neighbourhood marketplace — depreciation pricing, masked identity, UPI escrow.
- One identity
- Family graph with consent
- Address as a primitive
- One consent ledger
- WhatsApp-native notification mesh
03 / The flagship, concretely
Sayuk Tend runs a real hospital pharmacy.
Tend runs a real children's hospital today. The pharmacy is not a stub — it is a full counter. A walk-in sale starts from a name and a phone number, searches the shared catalog, builds a cart, and prints a GST invoice with the tax extracted from MRP.
Every tenant searches the same 2,46,000-medicine catalog and adopts an item the moment it is stocked. Suppliers, purchase orders, goods-receipt verification, and batch / expiry FIFO keep the shelf honest, with near-expiry alerts ahead of loss.
- Walk-in POS — counter sale, no prescription required
- 2,46,000-medicine FTS5 shared catalog, adopt-on-stock
- Suppliers → PO → GRN, batch / expiry FIFO + near-expiry alerts
- GST invoices, MRP-inclusive tax extracted to CGST / SGST
- Per-Indian-FY invoice numbers, monthly GSTR-1 summary
- Distributor CSV import, offline-tolerant SQLite-per-tenant
04 / How we work
Six rules we don't break.
- 01
Every product compounds on a shared substrate.
One identity, one family graph, one consent layer. We ship in parallel because each product makes the substrate richer, and a richer substrate makes the next product faster to build.
- 02
WhatsApp before app.
Until India shifts off WhatsApp, the product reaches people there. Reminders, confirmations and invoices arrive on the number they already use.
- 03
Offline-tolerant over a perfect SLA.
Flickery rural Wi-Fi is the real operating condition. Tend runs on SQLite-per-tenant so the counter keeps working when the line drops.
- 04
English-friendly, not English-required.
Indic name fields handled properly — no forced first / last splits. More Indian languages on the roadmap.
- 05
Honest about state.
Shipping, live, or alpha — every product wears its real state, here and on the home page. A visitor always knows what is real today and what is still early.
- 06
Built for the desk. Not the deck.
Every product earns its place through real use, not investor narrative. No procurement-decided features. No round to raise before the work is real.
We're not optimising for scale. We're optimising for the day a small-town doctor opens our app and it does what she needs without being asked twice.
— Sayuk · Hyderabad · 2026