Ahmedabad, India · IST (UTC+5:30)
A software studio from the city of looms.
Ahmedabad was once called the Manchester of the East. Its mills wove cloth for the world. We’re carrying that craft into software: patient, precise, and built to last.
- Studio
- Ahmedabad, Gujarat, India
- Hours
- Monday to Friday · IST (UTC+5:30)
- Works with
- Teams worldwide
01Origin
Computing was born on a loom.
The first machine to follow a program wove silk. We think that's the right lineage for a software company from the city of looms.
tānā · ताना · તાણો
noun · Hindi, Gujarati
The warp: threads set first on a loom and held under tension. Hidden in the finished cloth, they hold every pattern together. Tanaloom is the loom that sets them right.
- 1804
A loom learns to read
Joseph-Marie Jacquard patents a loom controlled by chains of punched cards. Each hole lifts a thread.
- 1837
The cards meet mathematics
Charles Babbage designs the Analytical Engine and borrows Jacquard's cards to program it.
- 1843
Weaving algebra
Ada Lovelace writes that the Engine “weaves algebraical patterns just as the Jacquard-loom weaves flowers and leaves.”
- 1890
Cards count a nation
Herman Hollerith's punched-card machines tabulate the US census: the start of data processing.
- Today
Back to the city of looms
Ahmedabad once wove cloth for the world. We weave software here, the same way: warp first, with care.
02Principles
The Weaver’s Code.
Five rules we hold ourselves to: in proposals, in code review and in hiring.
- 1
Set the warp first
Architecture comes before features. The strong threads you never see are the ones holding every pattern together.
- 2
Every thread accounted for
You see every commit, every decision and every hour. No black boxes, no surprise invoices.
- 3
Mind the selvedge
Cloth unravels at its edges, and so does software. Edge cases, failure states, accessibility and security are designed up front, not patched later.
- 4
Tension is a feature
Budgets for performance, cost and scope aren't obstacles. Held at the right tension, they make the work stronger.
- 5
Weave to last
Readable code, real documentation and a clean handover. We build for the team that comes after us, even when that team is you.
03The team
Every thread, held by a person.
Your project isn’t handed to “a team”. It’s woven by a small pod where every thread has an owner, and you’ll know each of them by name before the build begins.
The loom-keeper
Delivery lead
- Owns
- The plan, the weekly demo, the budget and your inbox.
- You get
- One person who always knows where things stand, and answers within a working day.
Sets the warp
Solution architect
- Owns
- The data model, integrations and security: every decision that is expensive to change later.
- You get
- An architecture you can read on one page, agreed before the build begins.
Draws the pattern
Product designer
- Owns
- Research, user flows, the interface and the design system.
- You get
- A clickable prototype before any code, and screens that ship the way they were drawn.
The weavers
Engineers
- Owns
- The build itself: web, mobile, back end and AI, in weekly passes.
- You get
- Working software every week or two, on a link you can click.
The reed
Quality engineer
- Owns
- Automated tests, accessibility and performance, checked on every change.
- You get
- Problems caught before they reach you, not in a testing phase at the end.
Take-up
Cloud & reliability
- Owns
- Infrastructure, releases, monitoring and security updates.
- You get
- Small, calm releases, and someone watching after launch.
How a pod is formed
Sized to the work, never padded. On a small project one person may hold two threads; on a large one, several people share one. Every thread always has an owner, and the people you meet at the start are the people who deliver.
We hire weavers, not typists.
People who care about the threads nobody sees: the data model, the error state, the handover note.