Skip to content
All work
Live in production
B2B SaaS · India
2026

Impex Info

Rescuing an unversioned production service

A B2B trade-intelligence service where importers search real customs records — a background worker scrapes the provider, builds an encrypted Excel report, uploads it and emails the customer.

Visit live site
impexinfo.com

Role

Sole developer

Client

Aashita Enterprises

Status

Live in production

Year

2026

4→1

Services consolidated

1

Service had no VCS at all

112k

Lines of code

3

Live subdomains

The hardest problem

The product was older than its repository. Four services were scattered across three separate repos — and one existed only as a single file sitting on the production server, with no version control of any kind.

What I did about it

01

Consolidated all four into one monorepo, so a change that spans the API and the media processor is one reviewable commit rather than a coordination problem.

02

Brought the unversioned production service under git without downtime, reconstructing its history from the deployed artefact.

03

Hardened auth on the way through — bcrypt, OAuth, JWT-secured APIs and per-site session isolation.

What I rejected, and why

A rewrite would have been cleaner and would have taken months during which the live product got no fixes. Consolidation-then-harden kept the revenue running.

What I’d change

Local development runs against the production database because no dev database was ever stood up. It worked because the team is one person, but it is one careless migration away from a very bad afternoon.

Built with

FlaskPythonPostgreSQLReact 18ViteRedux ToolkitChakra UIPhonePebcrypt

Next case study

Kayease Global

Agency site, HRMS and a Flutter attendance app