Developer Tools · India-readiness checks

BharatReady

Built for India, properly.

Find what breaks for Indian users: time-zone and financial-year bugs in your code, and Indian-language text that breaks your interface.

Fintech and e-commerce teamsApps launching regional languagesGlobal SaaS entering India

Book a BharatReady demo See pricing

bharat-ready · example

$ bharat-ready lint ./sample-app
HIGH   BR004 Financial year treated as the calendar year
HIGH   BR005 Rupee amount stored as a float
HIGH   BR009 Name validation that only allows English letters
MEDIUM BR001 Server-local date: wrong 'today' before 05:30 IST
2 files · score 14/100 · 8 high, 7 medium, 1 low
$ bharat-ready ui <our website> --scripts hi,ta,bn,ml
Hindi, Tamil, Bengali, Malayalam: 0 layout issues

Real runs: the sample app included with the product, and the UI test on our own website.

FindsIST, FY and format bugs

LanguagesIndian scripts

Runs onYour laptop, server or CI

OutputFixes with locations

The problem

Apps built with global tools break for Indian users in quiet ways: invoices dated yesterday, quarters starting in January, rupees in floats, Tamil names rejected by forms, Hindi buttons cut in half.

What it does

15 code rules for IST dates, financial year, Indian quarters, float rupees and GST rounding

Catches phone, name and pincode validation that rejects real Indian input

Flags Western number and date formats and code that strips Indian scripts

UI test fills pages with Hindi, Tamil, Bengali, Malayalam, Telugu, Kannada, Gujarati, Marathi or Urdu (right-to-left) text and finds cut-off, clipped and off-screen elements

Screenshots with every problem outlined, plus SARIF output for CI

How it works

Point it at your code, or at a running page
It scans the code and renders the UI in four Indian scripts
Fix the list, then gate CI on new issues

Works with

JavaScriptTypeScriptPythonJavaReact

Runs in your CI

GitHub Actions workflow step

- run: bharat-ready lint . --format sarif --out bharat.sarif --fail-on high
- uses: github/codeql-action/upload-sarif@v3
  with: { sarif_file: bharat.sarif }

Licensed customers get the action or command-line tool installed in their own organisation; it runs on your runners, so your code and plans never leave them. The command-line tools run in GitLab CI the same way.

Your data

Scans source locally.
Nothing is uploaded.
Findings point to file and line.

Who it's for

Fintech and e-commerce teamsApps launching regional languagesGlobal SaaS entering India

Questions

What kind of bugs?

Invoices dated yesterday, quarters starting in January, lakh and crore formatting, and text in Indian scripts that overflows or breaks.

Is it only for Indian companies?

It's for any product with Indian users.

Often used with BharatReady

Developer Tools

RunbookFinder

Engineering knowledge search

Answers your engineers can trust. Ask how a system works and get the runbook section, the postmortem and the code, with who owns it and whether it's out of date.

₹20,000–50,000View product → Developer Tools

TestHealer

Self-healing test fixes

Redesign without breaking tests. After a redesign, find every UI test selector that broke, the element it meant, and a verified fix as a diff. The same for API version bumps.

₹25,000–75,000 per suiteView product → Developer Tools

A11yReady

Accessibility audit

Accessible by design, compliant by law. Audit your website against WCAG 2.2 AA and see what each issue means under the European Accessibility Act, the ADA, and UK, Australian and Indian rules.

₹35,000–75,000View product →

← PreviousTenderMatrix Next →IndiaStackMock

See BharatReady on your own data

A 30-minute call. We run the product on your export, repository or document and walk you through the results.

Book a demo