| sort | uniq -c | sort -rn | head -20\n\n# who has committed, and how much\ngit shortlog -sn --since=\"1 year ago\""},{"t":"p","x":"If one person authored most commits to core modules, record it as people risk."},{"t":"h","x":"Infrastructure and operations"},{"t":"l","x":["Accounts: who owns the cloud, domain registrar, DNS and email accounts. They should belong to the company, with more than one administrator.","Environments: separation between production, staging and development, and whether production data is copied into lower environments.","Deployment: how releases happen, how often, and how they are rolled back. Manual SSH deployments are a risk to note, not a reason to walk away.","Backups: what is backed up, where, how often, and when a restore was last tested.","Monitoring: whether the team knows about outages before customers do.","Costs: monthly infrastructure spend, its trend, and the main cost drivers. Unexplained growth often points to waste or design problems.","Availability history: incident records, postmortems and any service levels promised in customer contracts."]},{"t":"h","x":"Security"},{"t":"p","x":"Security findings often have the largest effect on valuation and deal terms, because a breach after closing is the buyer’s problem."},{"t":"l","x":["Authentication: password storage, MFA for admin users, and session handling.","Access control: whether customers’ data is isolated properly in a multi-tenant system. Ask how tenant isolation is enforced and test it if permitted.","Secrets: credentials in source code or shared documents. Tools such as gitleaks or truffleHog scan history quickly.","Vulnerabilities: results of dependency scanning, such as npm audit, pip-audit or Dependabot alerts, and any past penetration tests with evidence of fixes.","Data protection: what personal data is stored, where, for how long, and under which agreements. In India, the IT Act and its rules on sensitive personal data apply. For European customers, GDPR obligations may follow the data.","Incidents: any past breaches, how they were handled, and whether customers or regulators were notified."]},{"t":"h","x":"Open-source licences and IP ownership"},{"t":"p","x":"Licence problems are invisible until someone looks, and expensive afterwards."},{"t":"l","x":["Generate a list of all dependencies and their licences. Tools such as license-checker for npm, pip-licenses for Python and FOSSA or ScanCode for larger estates help.","Flag copyleft licences, especially GPL in distributed software and AGPL in network services. These can require releasing source code in some circumstances.","Check for code copied from other projects without its licence, and for vendored libraries with modified licences.","Check newer source-available licences, such as SSPL or the Elastic License, if the product is offered as a service using those components.","Confirm IP assignment. Every employee and contractor who wrote code should have signed an agreement assigning IP to the company. Missing contractor agreements are one of the most common findings."]},{"t":"c","x":"# Node.js: summarise licences in production dependencies\nnpx license-checker --production --summary\n\n# Python: list licences of installed packages\npip install pip-licenses\npip-licenses --format=markdown --order=license"},{"t":"h","x":"People, process and documentation"},{"t":"p","x":"Technology risk is often people risk."},{"t":"l","x":["Key-person dependency: which systems only one person understands. Ask each engineer, \"If you were away for a month, what would break?\"","Team structure: employees versus contractors, notice periods and retention arrangements for key engineers.","Process: how work is planned, reviewed and released. Code review on every change is a good sign. Direct commits to production branches are a risk.","Documentation: runbooks for deployment, incident response and common operations. Even short ones show maturity.","Roadmap realism: compare the product roadmap with team size and past delivery speed."]},{"t":"h","x":"Writing up findings"},{"t":"p","x":"A useful report is short and ranked. For each finding, record what was found, the evidence, the risk to the deal, and the estimated effort to fix. Group findings into three levels:"},{"t":"l","x":["Deal-critical: issues that should change terms or block closing until fixed, such as IP not owned by the company or a serious unpatched vulnerability exposing customer data.","Fix within 100 days: issues that need a remediation plan as a condition or covenant, such as single-person access to production or untested backups.","Track: technical debt and process gaps that affect future cost but not the decision."]},{"t":"p","x":"Include positive findings too. A clear architecture, a working CI pipeline and tested restores are evidence that the team can execute."},{"t":"h","x":"Condensed checklist"},{"t":"l","x":["Company owns code repositories, cloud accounts, domains and DNS, with more than one admin.","Product builds and runs from documentation by someone other than its author.","Automated tests run in CI on critical paths.","Backups exist and a restore has been tested recently.","No secrets in source history. MFA on all admin accounts.","Tenant data isolation is enforced and has been tested.","Dependency licences listed, copyleft use understood, and IP assignment signed by all contributors.","Key-person risks identified, with mitigation.","Infrastructure costs understood and in line with usage.","Findings ranked as deal-critical, fix within 100 days, or track, with effort estimates."]},{"t":"p","x":"A good review does not look for a perfect company. It looks for an honest picture of the risks and what it would take to address them."}]
Infigini IT Services
Infigini IT Services
{{ pageBg }}
Infigini IT Services · Dehradun, India

Software, cloud and AI systems, built to last.

Infigini designs, builds and operates custom software for universities, healthcare providers and enterprises. Our work ranges from ERP platforms and AI knowledge assistants to the cloud infrastructure they run on.

{{ s.v }}
{{ s.l }}
{{ marquee }}
Services

Nine disciplines, one engineering team.

The same team handles architecture, build and production, so nothing is lost passing work between departments.

Popular {{ l.nav }}
Selected work

Systems in production.

All {{ projectCount }} projects →
Our products

We also build products of our own.

Two proprietary platforms we own and operate, plus open-source libraries published on GitHub and npm. The patterns we recommend to clients come from running them.

How we work

A written architecture before any code is written.

{{ s.n }}
{{ s.t }}
{{ s.d }}
Read about our process →
Engineering stack

The technologies we use, organised by layer.

{{ l.k }} {{ l.v }}
About Infigini

IT systems that organisations depend on every day.

Infigini IT Services builds software that simplifies infrastructure management and supports new ideas. We work with developers and organisations to build, deploy and scale their systems, with a focus on security, scalability and ease of use.

Our work covers campus ERPs used by thousands of students, AI assistants on Azure, appointment systems for clinics and hospitals, and the cloud servers they run on. We look after these systems from the first requirement through years of production.

{{ s.v }}
{{ s.l }}
Mission

To give organisations scalable IT systems that simplify infrastructure management, so that businesses of any size can work more efficiently and grow faster.

Vision

To become a global provider of next-generation IT solutions that integrate advanced technology into everyday operations.

Our values

{{ v.n }}
{{ v.t }}
{{ v.d }}
Industries

The sectors we work in.

Services

Services built around your operations.

One engineering team covers architecture, build and production operations. Choose a single discipline, or bring us in for the whole system.

{{ s.n }} {{ s.title }} {{ s.short }} {{ s.stackLine }} Learn more →
Specialised services

Looking for something specific?

← All services
Service {{ svc.n }}

{{ svc.title }}

{{ svc.long }}

What's included
—{{ it }}
Technologies
{{ t }}

Specific services

Related projects

← {{ land.backLabel }}
{{ land.eyebrow }}

{{ land.title }}

{{ land.intro }}

Loading…

Sound familiar?

{{ land.problemsTitle }}

{{ x.t }} {{ x.d }}
What's included

{{ land.includesTitle }}

{{ x.n }} {{ x.t }} {{ x.d }}
Ways to work with us

{{ land.plansTitle }}

{{ pl.name }} {{ pl.for }}
—{{ it }}
Ask about this →
How it works

{{ land.stepsTitle }}

{{ st.n }} {{ st.t }} {{ st.d }}
Why Infigini

{{ land.whyTitle }}

{{ w.t }} {{ w.d }}
Technologies we use
{{ t }}

Related work

FAQ

Questions we get asked.

{{ f.q }}+

{{ f.a }}

Further reading
Related services
Industries

Industries we build for.

Most of our work is for organisations whose systems carry real operational weight: campuses with thousands of students, clinics booking patients all day, and enterprises whose HR and finance processes cannot stop. These pages cover what we build for each sector.

{{ s.n }} {{ s.title }} {{ s.short }} Learn more →
Projects · {{ projectCount }}

Our work, from 2020 to today.

This list covers our platforms, client systems and open-source libraries. Client names are withheld at their request.

{{ p.year }} {{ p.title }}{{ p.client }} {{ p.summary }} {{ p.cat }} →
← All projects
{{ proj.cat }} · {{ proj.year }}

{{ proj.title }}

{{ proj.summary }}

{{ proj.shotAlt }}
Client{{ proj.client }}
Year{{ proj.year }}
Category{{ proj.cat }}
Stack
{{ t }}
Visit live ↗
The work

{{ proj.body }}

{{ pt.n }}{{ pt.x }}
Context

{{ proj.ctxText }}

The challenge
{{ c.n }}{{ c.t }}{{ c.d }}

What we built

{{ b.n }}{{ b.t }}{{ b.d }}
How it fits together

{{ proj.architecture }}

Why this stack
{{ t.t }}{{ t.d }}
Related services and reading
Products

Platforms we run. Libraries we publish.

TechLogHub and EasySiteControl are proprietary platforms that Infigini owns and operates. Our open-source libraries are on GitHub and npm for anyone to use, and we use them in client projects too.

Proprietary platforms
Proprietary · Live{{ p.year }}
{{ p.title }}
{{ p.summary }}
{{ p.stackLine }}
Open-source libraries · GitHub & npm
{{ l.title }}
{{ l.year }} · {{ l.stackLine }}
{{ l.body }}
How we work

Five stages, from first conversation to production.

Each stage ends with a deliverable you keep. You get software you can use every two weeks, so nothing important arrives as a surprise at the end.

{{ s.n }} {{ s.t }} {{ s.d }} You receive{{ s.out }}

Engagement models

{{ m.t }}
{{ m.d }}
Journal · {{ postCount }} articles

Notes from the engineering team.

Practical write-ups on cloud and DevOps, AI systems, ERP platforms and the frontend and backend work behind them, plus guides for teams planning a software project.

Latest · {{ leadPost.cat }} · {{ leadPost.date }} · {{ leadPost.read }} read
{{ leadPost.title }}
{{ leadPost.dek }}
Read article →
{{ p.cat }}{{ p.date }}
{{ p.title }}
{{ p.dek }}
{{ p.read }} read →
← Journal
{{ post.cat }} · {{ post.updatedText }} · {{ post.read }} read

{{ post.title }}

{{ post.dek }}

{{ post.byline }}
Glossary

Terms we use, in plain English.

Short definitions of {{ glossCount }} cloud, DevOps, AI, data, security and business software terms, each with an example and links to the guides and services where it matters.

{{ g.letter }}
FAQ

Common questions.

These cover scope, timelines, ownership and what happens after launch. If your question isn't here, write to us.

{{ f.a }}

Contact

Tell us what you are building.

A few sentences are enough to start. We reply within one business day.

Registered office11 Shree Ram Puram Lane No.2,
Kanwali Road, Dehradun,
Uttarakhand 248001, India
GSTIN05AAIFI1118B1Z3
Book a free 15-minute review ↗ Prefer to talk? Bring your setup or roadmap; you get the top 3 fixes in writing.
What happens next
{{ s.n }}{{ s.t }}{{ s.d }}
Enquiry about{{ topic }}

{{ err }}

We use your details only to reply to this enquiry. See our privacy policy.

Thank you. We have your message.

An engineer will reply within one business day.

Legal

{{ legalTitle }}

Last updated 9 November 2026

{{ s.h }}

{{ s.p }}

{{ x.eyebrow }}

{{ x.h }}

{{ it.t }} →{{ it.d }}
{{ it.t }}{{ it.d }}

{{ ctaLead }} Let's talk.

Discuss your project →
Talk to us
Talk to an engineerWe reply within one business day.
Book a free 15-minute reviewPick a time on Cal.com Send us a messageTell us what you are building Call +91 95684 87789Speak to us directly [email protected]Email us directly