Portfolio
Selected capabilities & delivery areas
This page describes the categories of production work Aquarius Infotech undertakes, and the technical decisions each involves. It does not name clients, because we do not publish client work without written permission.
If you are evaluating us, the useful conversation is about your problem and our relevant experience with it — which we can discuss in far more detail privately than any public page would allow.
Confidentiality
Selected client work may be subject to confidentiality, contractual restrictions or publication permissions. Public examples are shared only where disclosure is authorized. Where a prospective client needs evidence of relevant experience, we provide technical detail and, where the client concerned has agreed, a reference contact — under a mutual confidentiality agreement rather than on a public page.
Delivery area 01
Mobile applications
Native Android products taken from architecture through to a repeatable release process. The work concentrates on the parts of Android that decide whether an application behaves the same on a test device and on a constrained handset with aggressive battery management.
Consumer utility applications
Applications with substantial background behaviour: scheduled work, connectivity-triggered sync, notification handling and state that must survive process death.
Content and media applications
List-heavy interfaces with paging, caching and offline reads, where scroll performance and memory behaviour on mid-range devices decide whether the product feels usable.
Ad-supported applications
Products monetised through in-app advertising, where placement, mediation configuration and revenue reporting have to line up with acquisition cost on the same definitions.
Applications with backend dependency
Clients of an API we also build, designed together so that retry, idempotency and offline behaviour are decided once rather than negotiated across a boundary.
Existing codebase takeover
Audit of architecture, dependency and target API status, crash and ANR history, background behaviour and release configuration, followed by prioritised remediation.
Release and compliance work
Target API level increases, permission and data safety disclosure updates, and staged rollout configuration carried out ahead of enforcement deadlines where notice allows.
Detail on this practice: mobile app development.
Delivery area 02
Backend & API systems
Services with an explicit contract, so a client application can be written against a specification rather than against observed behaviour, and so a failure degrades rather than cascades.
REST API services
Resource modelling, versioning, error semantics, pagination and bulk operations, with idempotency designed in for anything that will be retried.
Containerised microservices
Services packaged so the environment a developer runs is the environment production runs, with health checks, graceful shutdown and configuration held outside the image.
Authentication & authorisation
Token issuance and refresh, service-to-service credentials, role and permission modelling, and least-privilege access to hosts and databases.
Integration services
Backends that mediate third-party APIs, absorbing rate limits, retries and vendor-specific error behaviour so client applications do not have to.
Database work
Schema design, indexing, query optimisation, connection pooling and transaction behaviour — usually the first place a performance problem is actually located.
Legacy backend takeover
Assessment of service boundaries, deployment process, backup and restore status and monitoring coverage, delivered as a written risk list before any change.
Detail on this practice: cloud & API engineering.
Delivery area 03
Analytics & measurement systems
The layer that decides whether any later claim about performance can be defended. Most of this work is definition work before it is implementation work.
Event schema design
Event names, firing conditions, parameters and values defined in writing, including which events are conversions and which are diagnostic only.
GA4 and Firebase implementation
Property and data stream configuration, conversion definitions, audience creation and platform linking, verified against real traffic before it is relied on.
BigQuery pipelines
Export and query layers for analysis the platform interfaces do not support, including cohort behaviour and monetisation reporting.
Server-side measurement
Backend confirmation of conversion values — net of cancellations and refunds where relevant — and delivery into platforms through the appropriate import path.
Deduplication & reconciliation
Rules that stop a retry becoming a second conversion, and reconciliation between platform-reported and backend-recorded figures with the gap explained.
Measurement audit
Review of an existing implementation to establish what is actually being recorded, what is double counted and which reported numbers cannot currently be defended.
Delivery area 04
Performance advertising systems
Google Ads programmes run as an independent agency under authorisation from the advertiser, with the account structure, measurement and commercial reporting treated as one system rather than three.
Account structure & governance
Campaign and account architecture, Manager Account linkage and access governance at the permission level the engagement requires.
App acquisition programmes
App campaigns built on the Firebase events the application actually emits, with value-based optimisation used only where event values are reliable.
Search demand capture
Keyword and intent structure, match type strategy, negative lists, search term review and landing page alignment.
Display, video and Performance Max
Audience planning, creative testing, placement review, and automated campaign types used selectively where conversion data supports them.
Verification & policy workflow
Assistance with advertiser verification workflows and with responding to policy notices, within the limits set out on our transparency pages.
Commercial reporting
Reporting that keeps platform media cost separate from agency service fees, traceable back to campaigns and dates.
Detail on this practice: Google Ads management. How the agency relationship works: agency–client relationship.
Delivery area 05
Infrastructure & deployment
Environments that can be rebuilt by someone who did not originally build them, and that report their own state rather than waiting to be asked.
Linux server provisioning
Host setup and hardening, service accounts, firewall configuration and closed administrative surfaces.
OpenLiteSpeed & CyberPanel
Web layer provisioning, virtual host configuration, TLS termination and LiteSpeed Cache tuning for the workload in question.
Reverse proxy & edge
Routing, compression, connection tuning and rate limiting handled at the edge rather than inside application code.
Deployment procedure
A repeatable deploy and rollback path, documented rather than held in one person's memory.
Monitoring & alerting
Log aggregation, health monitoring and alerts set on conditions that would actually require someone to act.
Backup & restore
Backups configured and restores actually tested, because an untested backup is an assumption rather than a control.
Questions
About this page
Why are there no named clients on this page?
Because we do not publish client names, screenshots, account identifiers or performance data without written permission, and permission has not been granted for public publication. Naming clients without that permission would breach the confidentiality we offer every client, including any future one.
Can you show relevant experience during an evaluation?
Yes. Under a mutual confidentiality agreement we can discuss relevant engagements in technical detail, walk through architecture and measurement decisions, and where a client has agreed, provide a reference contact. That happens in the evaluation conversation rather than on a public page.
Will verified projects be published here later?
Where a client authorises publication, yes. This page is structured so a verified entry can be added without redesigning it. Nothing will appear here that has not been approved in writing by the client concerned and that we cannot support with our own records.
Discuss a project
Ask about experience relevant to your problem
Tell us what you are building and we will discuss comparable work in technical detail, under a mutual confidentiality agreement where that is appropriate.
- Telephone
- +91 87800 2787
- Principal place of business
- 3rd Floor, Office No. 309, Cyber City
VIP Circle, Mota Varachha, Utran
Surat, Gujarat 394105, India - Accountable person
- Gopal Savaliya — Founder & Managing Director