The platforms we build on
We work with platform vendors whose products end up inside client projects. A technology partnership means we know your product properly and you know we will not misrepresent it.
What we build on today
These are the platforms our engineers work with regularly enough to deploy without a learning curve on your budget.
- Cloud: AWS, Google Cloud, Hostinger and DigitalOcean
- Data: PostgreSQL, MySQL, Redis and Elasticsearch
- Payments: Razorpay and Stripe
- Identity: Auth0, Keycloak and the major cloud identity services
- Frontend: React, Next.js, Vue and plain TypeScript where a framework is overkill
- Mobile: React Native and Flutter
What a partnership involves
Less ceremony than the word suggests. In practice it means our engineers are trained on your product, we have a technical contact when something is unclear, and we do not recommend you for work you are wrong for.
- At least two engineers certified or demonstrably fluent in the product
- A technical contact on your side for escalation
- Early access to release notes, so we do not discover breaking changes from a client
- A commitment from us not to recommend the product where it is a poor fit
What we will not do
We do not accept commission for recommending a platform to a client. If a platform pays for placement, the recommendation is worth nothing to the client and eventually costs us the relationship. Partnership gets you our engineers' familiarity, not our advocacy.
Adding a platform
If your product fits work we already do, the useful starting point is technical rather than commercial: give two of our engineers access and documentation for a fortnight and let them build something real with it. We will tell you honestly what was hard.
Questions we get asked
No. A recommendation that pays us is not a recommendation, and clients work that out. Partnerships get us training, support and early notice of changes, which is worth more over time than a referral fee and does not compromise what we tell a client.
Usually yes, if a client needs it, and that work is quoted to the client in the normal way. We also build integrations speculatively where a platform is clearly heading into work we do often. That is a conversation rather than a commitment, and it starts with the two-week technical evaluation.
Documentation that matches the current version, a sandbox that behaves like production, and a human to ask when the documentation is wrong. Those three are more valuable than co-marketing, and their absence is the usual reason an integration takes three times the estimate.
What clients say on Google
Unedited, pulled live from our Google Business listing.
Loading reviews from Google - read them on Google.
Building a platform we should know?
Tell us what it does and where it fits, and we will say whether it overlaps with work we already do.
- USD
- EUR
- GBP
- CHF
- SGD
- AUD
- CAD
- AED
- SAR
- QAR
- JPY
- INR
Card, netbanking, wallet and UPI through Razorpay, which is what our checkout runs on, so anything it accepts we accept. Bank transfer, SEPA, Wise and Payoneer for invoices that prefer it.
NDA before the first call. Full IP assignment on delivery. Contracts under Indian, English or Delaware law.