01
Modules declare. The platform resolves. Workspaces compose.
People experience workflows, not integrations. A restaurant bill reaching a hotel folio is the platform doing its job, not a connector someone has to maintain.
The story of
Built the other
way round.
began with a frustration: organisations are too often made to reshape how they work around the software they buy. The hotel bends to its system, the club keeps a second record because the first cannot hold a family, the school runs its sport somewhere its students are not.
So I set out to build it the other way round—connected Operating Systems designed around how organisations actually operate, each built for one kind of organisation, all standing on one foundation of people, money and records.
Looking for the products themselves? arthavya.schinchela.com ↗
How it got here
Where it started
AllianceOS
The first version: a platform for associations and member organisations—membership, HR, approvals, documents and a serious finance engine—built around one client.
15 August 2026
goes public
On Independence Day the work took its own name, and a promise: engineered in Bharat, built for the world.
28 August 2026
Starting again, properly
A clean foundation—tenant, legal entity, organisation unit; deny by default; one ledger that only Finance writes. The first version became a source of knowledge, not code.
September – October 2026
Nine Operating Systems
Hotels, restaurants, clubs, associations, firms, retailers, hospitals, schools and sports venues—each built for one kind of organisation, all on the same people, money and records.
20 October 2026
A new public home
arthavya.schinchela.com: every picture on it drawn from the product's own data.
What the first version taught me
Preserve the knowledge. Generalize the implementation.
AllianceOS was serious software. Its finance engine, its tax logic and its membership rules held hard-won domain knowledge. But too much of it assumed one customer, in one country, in one industry.
So every capability in faces one question before it reaches the core:
Would this design still make sense if the next customer were in a completely different industry?
The other lesson was smaller and sharper: a setting that nothing reads is worse than no setting at all. If something is configurable, the product must actually honour it.
How it is built
Four rules the code is not allowed to break.
02
Finance owns the truth.
Operations publish what happened; only posting writes the ledger. That is why every product has its books from day one, and why there is only ever one set of them.
03
A country is a pack, not the core.
India's GST, TDS, e-invoices and e-way bills live in an India country pack. The core stays free of any one country's rules—that is what built for the world means in code.
04
One client, everywhere.
The web, the Windows app and the Android app are the same client on the same API. There is no second app to fall behind, and no business logic hiding in a phone.
In the names
Words from home, for work anywhere.
अर्थ (artha) is the Sanskrit word for meaning, purpose and wealth. The name is drawn in two scripts at once, Devanagari and Latin—never one without the other.
Each Operating System carries a word that says what it is for.
Atithya आतिथ्य
hospitality
Anna अन्न
food, grain
Sabha सभा
an assembly, a gathering
Sangha संघ
an association, a union
Yukti युक्ति
reasoning, skill
Vyapaar व्यापार
trade
Arogya आरोग्य
health
Vidya विद्या
knowledge, learning
Khelan खेलन
play
The mark is six nodes and seven lines. The nodes are the master brand, not a count of products—so the mark never changes when a product is added.
Even the colours keep time. The product's light follows India's six seasons—Vasanta, Grishma, Varsha, Sharad, Hemanta and Shishira. Right now it is Hemanta: diyas, gold and sindoor.
Eight weeks in · 20 October 2026
- weeks since the clean start
- 8
- weeks since the clean start
- commits
- 2,961
- commits
- automated tests passing
- 7,600+
- automated tests passing
- Operating Systems on one ledger
- 9
- Operating Systems on one ledger
One principle runs through every screen.
Complex systems should feel simple to the people using them.
A bartender pours a round, a scorer taps a point, a front desk checks a guest out: the complexity is 's to carry, never theirs.
Engineered in Bharat. Built for the world.
Run a hotel, club, school, firm or hospital? I will walk you through it myself. More about me