Cyber City, VIP Circle, Mota Varachha, Surat, Gujarat 394105

Technology

The stack we build, deploy and measure with

These are the technologies our engagements are actually delivered on, and what each is used for. It is a working list rather than a capability inventory: if something is not here, we will say so at scoping.

Layer 01

Mobile

Native Android. We do not present ourselves as an iOS or cross-platform shop, and where a project needs those we say so rather than accepting the work.

Languages & SDK

Kotlin Java Android SDK Coroutines Gradle
  • Kotlin for new code; Java maintained where an existing codebase uses it.
  • Coroutines for structured concurrency and cancellation tied to lifecycle.
  • Gradle build types and product flavours for reproducible release configuration.

Framework & storage

Jetpack Room WorkManager Firebase FCM
  • Jetpack lifecycle-aware components for state that survives configuration change and process death.
  • Room for local persistence, with explicit schema migrations rather than destructive fallback.
  • WorkManager for deferrable and constrained background work across API levels and OEM behaviours.
  • Firebase for analytics, crash reporting, remote configuration and push messaging.

Layer 02

Backend

Service runtimes chosen for the workload rather than by default, behind an API contract written before implementation begins.

Runtimes & interfaces

Node.js Python PHP REST APIs API gateways
  • Node.js for I/O-bound services and event ingestion paths.
  • Python for data processing, pipeline and analysis work.
  • PHP where an existing environment or platform requires it.
  • REST with explicit resource modelling, versioning, error semantics and idempotency for retried operations.

Data & access control

MySQL / MariaDB Schema design Query optimisation Token auth Rate limiting
  • Relational schema design with indexing and query plans reviewed before capacity is added.
  • Connection pooling and transaction behaviour treated as design decisions, not defaults.
  • Token-based authentication with refresh, service-to-service credentials and role modelling.
  • Rate limiting and abuse controls applied at the edge rather than inside application code.

Layer 03

Infrastructure

Built on Linux hosts rather than bound to one provider's managed services, so a deployment stays portable. Where a client has standardised on a provider, we work inside that environment.

Packaging & hosts

Docker Containerised microservices Linux Reverse proxy
  • Docker images with multi-stage builds; configuration and secrets held outside the image.
  • Health checks and graceful shutdown so a rollback is a deployment rather than a repair.
  • Linux host provisioning and hardening, least-privilege service accounts, closed administrative surfaces.
  • Reverse proxy for routing, TLS termination, compression and connection tuning.

Web layer & operations

OpenLiteSpeed LiteSpeed Cache CyberPanel Caching Monitoring Backups
  • OpenLiteSpeed and CyberPanel for provisioning, virtual hosts and TLS on managed environments.
  • LiteSpeed Cache tuned to the workload, with invalidation rules defined rather than assumed.
  • Log aggregation and alerting set on conditions that would actually require someone to act.
  • Backups configured and restores tested, because an untested backup is an assumption.

Layer 04

Analytics

The layer that decides whether a later performance claim can be defended. Most of the work is definition before it is implementation.

Collection

Google Analytics 4 Firebase Analytics Conversion tracking Server-side events
  • GA4 property and data stream configuration, event and conversion definitions, audience creation and platform linking.
  • Firebase event instrumentation in-app, with firing conditions and values agreed in writing first.
  • Conversion actions with value assignment and deduplication so a retry does not become a second conversion.
  • Server-side confirmation of values where the client environment requires it.

Analysis

BigQuery Export pipelines Cohort analysis Reconciliation
  • BigQuery exports and queries for analysis the platform interfaces do not support.
  • Cohort and retention analysis across acquisition source and product behaviour.
  • Reconciliation between platform-reported and backend-recorded figures, with the gap explained rather than ignored.

Layer 05

Advertising & monetisation

Acquisition and in-app revenue treated as one system, so cost and revenue can be compared on consistent definitions rather than reconciled across disconnected dashboards.

Acquisition

Google Ads App campaigns Search Display & Video Performance Max
  • Google Ads account and campaign structure, Manager Account linkage and access governance.
  • App campaigns optimised against Firebase events the application actually emits.
  • Search, Display and Video where the objective is measurable; Performance Max used selectively where conversion data supports it.

Monetisation

AdMob TradPlus TopOn Ad revenue reporting
  • AdMob integration, ad format placement and policy-relevant configuration.
  • Mediation through TradPlus or TopOn where an application uses it.
  • Ad revenue events reported into analytics so revenue and acquisition cost share definitions.

On third-party platforms

Availability, features, pricing and policies of the platforms named on this page are controlled by their respective providers and may change at any time. We work within those terms; we do not control them and cannot vary them. Google, Google Ads, Google Play, Android, Firebase, AdMob and BigQuery are trademarks of Google LLC; other product names belong to their respective owners. Aquarius Infotech is an independent service provider and holds no vendor certification, partnership or endorsement in respect of any technology listed here.

Questions

About our stack

Do you work with technologies not listed here?

This page lists what we use in production rather than everything we have touched. If a project needs something outside it, we will say so at scoping instead of learning on your engagement — and where the right answer is a different provider, we will say that too.

Why Linux hosts rather than a provider's managed services?

Portability. Building on Linux virtual machines and container hosts keeps a deployment movable between providers rather than bound to one vendor's proprietary services. Where a client has already standardised on a provider, we work within that environment.

Are you certified in any of these technologies?

We hold no vendor certification and claim none. Where a client requires a certified provider for a particular platform, that is a legitimate requirement and we will say plainly that we do not meet it rather than describing our experience in a way that implies certification.

Technical fit

Check whether we are the right team

Describe the system and the constraints. If your problem sits outside this stack we will tell you, rather than taking the work and learning on it.

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