Technology

Choose technology for the operating problem

Our technology page describes tools and engineering areas we work with without assigning subjective “Expert” scores, claiming blanket regulatory compliance or turning product-vendor usage into a partnership claim.

Web applications

Modern web interfaces and business applications using typed, component-based development approaches.

ReactNext.jsTypeScriptTailwind CSSHTML / CSS

Backend & APIs

Server-side services, integrations and APIs for business and product workflows.

Node.jsPythonREST APIsApplication integration

Data systems

Relational, document and caching technologies selected according to data model and operating requirements.

PostgreSQLMySQLMongoDBRedisBackup & migration

Cloud & deployment

Hosting, containerisation and deployment automation for applications that need maintainable operations.

AWSOracle CloudDockerCI/CDMonitoring

Networks & connectivity

Infrastructure experience that connects application delivery with the networks and sites where systems actually operate.

IP networkingLAN / WANWi-FiFTTH / GPONFiber systems

Mobile delivery

Mobile and responsive experiences when business workflows need access beyond the desktop browser.

AndroidResponsive webProgressive web appsAPI-backed mobile workflows

Engineering principles

What matters beyond the framework name

Technology choices are only useful when the resulting system is secure enough, operable, testable and supportable.

Security by design

Use authentication, authorisation, encryption, access controls and logging appropriate to the system risk. Regulatory compliance is assessed against the specific product, data and jurisdiction rather than claimed generically.

Least privilege & data minimisation

Limit access and data collection to what the system genuinely needs, and separate sensitive functions where practical.

Operational maintainability

Plan deployment, monitoring, backup, recovery and change management alongside application development.

Infrastructure awareness

Account for bandwidth, power, physical sites, network topology and connected hardware when software depends on real-world infrastructure.

Technology evidence

A technology is listed because it is used or relevant to our delivery work—not because SarvaLaxmi is claiming vendor certification, partnership or top-tier proficiency in every listed tool.

Credentials are separate

Corporate registrations and individual professional credentials are shown separately so visitors can distinguish the company’s legal status from a team member’s qualifications.

View credentials