Skip to content

Partners & platforms

The technology we build on

We're deliberately not locked to one vendor. These are the platforms we work with day to day, chosen per project on merit rather than on which programme pays us the most.

Our position on vendors

Plenty of IT firms are structurally incentivised to recommend one cloud, because their margin comes from reselling it. We'd rather keep the advice clean: wherever possible, infrastructure is provisioned in your own accounts, billed directly to you by the vendor, with no markup passing through us.

That means if you outgrow us, you keep everything and change nothing. It also means when we recommend a platform, the only reason is that it fits the problem.

We don't currently claim any formal partner tiers or certification badges. When we hold one, it will be listed here with its level and nothing more — no logo wall implying relationships we don't have.

What we work with

Grouped by the job it does, not by vendor relationship.

Cloud & infrastructure

Where applications actually run. Chosen per workload — data residency, managed-service depth and cost profile differ more than the marketing suggests.

  • Amazon Web Services
  • Microsoft Azure
  • Google Cloud
  • Cloudflare
  • DigitalOcean
  • Hetzner
  • cPanel / WHM
  • Kubernetes
  • Docker
  • Terraform

Data & AI

Storage, pipelines and model providers. We default to open, portable formats so your data is never trapped inside a vendor's proprietary layer.

  • PostgreSQL
  • Redis
  • MySQL / MariaDB
  • ClickHouse
  • Elasticsearch
  • Anthropic Claude
  • OpenAI
  • Metabase
  • Apache Airflow

Application & web

The stack most of our engineering work is built in, plus the CMS and commerce platforms clients most often already run.

  • TypeScript
  • Next.js / React
  • Node.js
  • Python
  • React Native
  • Flutter
  • WordPress
  • WooCommerce
  • Shopify
  • Laravel

Communication networks

Message delivery reaches carriers through an upstream aggregator and the platform owners' own business APIs. Routes and fallbacks are configured explicitly, never left to chance.

  • WhatsApp Business Platform
  • RCS Business Messaging
  • SMPP carrier routes
  • Upstream CPaaS aggregator
  • Resend
  • SMTP / DKIM / SPF

Payments & commerce

Indian and international rails, so a single build can take money from UPI and from a card issued anywhere.

  • Razorpay
  • UPI
  • Stripe
  • PayPal
  • Visa / Mastercard / Amex
  • RuPay & NetBanking

Security & operations

The tooling behind monitoring, incident response and the audits we run for clients.

  • Cloudflare WAF & Turnstile
  • Let's Encrypt
  • Grafana
  • Prometheus
  • Sentry
  • OWASP ZAP
  • Vaultwarden / 1Password

Certifications & partner tiers

None claimed. We hold no formal partner tiers or vendor certifications today, and we'd rather say so than decorate this page with logos that imply a relationship we don't have. When we earn one, it will appear here with its programme and level.

How we choose

Four questions that decide the stack on every engagement, asked in this order.

  1. Can you leave?

    Exit cost is evaluated before adoption. Proprietary services are used where they're genuinely better, but never where the data model can't be exported or the workload can't be rehosted.

  2. Who operates it at 3am?

    A managed service that costs more but removes a pager rotation is usually cheaper than the self-hosted version. We price the operational burden, not just the licence.

  3. Where does the data live?

    Residency drives the region choice, not the other way round. For regulated Indian workloads that usually means in-country storage and a documented processing trail.

  4. What does your team already know?

    The best technology for a project is often the one your existing engineers can maintain after we hand it over. Novelty is a cost, and we count it.

FAQ

Partners & platforms

Are you an official partner or reseller of these platforms?

Not currently. We build on all of them, but we don't hold formal partner tiers and we don't claim badges we haven't earned. If that changes, this page will list the specific programme and level.

Do you resell cloud with a markup?

No. Wherever the vendor allows it, cloud accounts are opened in your name and billed directly to you, so you see the real invoice. The exception is our own hosting products, which are our service and priced as such.

Can you work with a platform that isn't on this list?

Usually. This is what we use most, not an exhaustive list of what we'll touch. If you're standardised on something else, say so during scoping and we'll tell you honestly whether we're the right team for it.

Who actually delivers the SMS and WhatsApp messages?

Delivery reaches carriers through an upstream aggregator we contract with, plus the platform owners' own business APIs for WhatsApp and RCS. We handle the integration, routing, fallback configuration and compliance; you get one API, one dashboard and one invoice.

Standardised on something specific?

Tell us what you already run. We'll be straight about whether we're a good fit for it, and what it would take.