We design, implement, integrate,and operate the softwareinfrastructure complex organisations run on.
A Bengaluru systems engineering practice. We design customer, employee, communication, analytics and intelligence interfaces around the workflows an organisation needs to run.
Five engagements. A connected estate.
A customer enquiry can create an employee task, trigger a permitted communication, update reporting and inform an approved next action. Each connection has agreed ownership and a delivery boundary.
Advisory
Architecture reviews, operating-model design, vendor evaluation, governance-gate design and procurement posture, before the build starts.Implementation
Greenfield and complex multi-entity rollouts on ERPNext, Frappe and Medusa — named lead, gated phases, predictable timeline.Migration
Migration assessments and cutovers from SAP, Odoo, Tally, Zoho, Shopify and other systems. Data, integrations, validation, rollback and ownership are scoped before delivery.Integration
Cross-system workflows between ERP, CRM, banking, government APIs, logistics and partner systems. Holisto IEP is in active engineering and may be selected where its fit is proven in scope.Managed services
Production operation, upgrades, observability and patching with agreed support boundaries, change windows and escalation paths.Named customers, regulated industries, multi-entity operators.
A non-exhaustive list of named, consented references. Outcomes and operating metrics are published only with a dated, customer-approved measurement basis.
Auditable numbers, structural facts.
Every metric carries its basis, sample and period, or says it can't be substantiated.
What we don't do — by design.
A practice that says yes to everything is a vendor — these limits are why our engagements land.
- Stand-alone consumer mobile apps.
- Pure brand design or creative campaigns.
- Marketing-as-a-service (campaigns, paid media, social ops).
- Per-product SaaS reselling under our name.
- Engagements without a principal consultant on the work.
Source, data, and infrastructure sovereignty
Not a marketing line. A contract.
Codebase, database and backups are yours, on infrastructure you control — no proprietary lock-in, per-export fee, exit penalty or “enterprise tier” upsell three months in. Hand-over documentation is part of the deliverable from day one.
The system you paid to build is yours: another practice can run it, you can take it in-house, and it outlives the engagement. That is the procurement posture a regulated buyer expects.
We fix the platforms we implement, not just deploy them.
Every row is a real upstream pull request or issue, verifiable in thirty seconds.
2 merged · 29 open pull requests, read live from GitHub — not typed in.
Synced 2026-08-13
Software we run ourselves, released for anyone to run too.
Our own authorship and repos, MIT-licensed.
- mithtech-is/Pulse
Agile project management inside Frappe/ERPNext — sprints, Kanban, epics, releases, OKRs, risks, retros and timesheets, all on native Project and Task records instead of a bolted-on app.
PythonMIT - suparikoli/medusync
Two-way sync between a Frappe/ERPNext site and a Medusa v2 backend — pick which doctypes sync from the Desk UI instead of hand-writing a payload template per doctype. Site-agnostic: no customer-specific fields baked in.
PythonMIT - suparikoli/ntfynext
Delivers Frappe notifications as ntfy push notifications alongside email, never as a replacement — per-user opt-in, escalating-backoff retries, a redacted delivery log, and a provider interface for adding Telegram or Discord later.
PythonMIT