Service
Cloud and support
APIs, integrations, hosting and the quiet work that keeps all of it running after launch.
What we build
The work, listed plainly.
- 01
APIs and integrations
Payment gateways, SMS and OTP providers, accounting systems, CRMs. Including the retries and the reconciliation nobody thinks about until money is missing.
- 02
Hosting and deployment
Set up on AWS or your provider of choice, with environments for staging and production and a rollback that takes a minute.
- 03
Maintenance
Security patches, dependency updates, certificate renewals and backups that have actually been restored at least once.
- 04
Monitoring
Uptime checks, error alerts and a monthly report in plain language rather than a wall of graphs.
What it is made of
- AWS
- Docker
- GitHub Actions
- Nginx
- PostgreSQL
- Redis
- Sentry
- Cron
What you are left with
At the end, these are yours.
A named contact
One person who knows your system, not a shared inbox and a ticket number.
A response window
Agreed in writing before the retainer starts, and different for a full outage than for a cosmetic bug.
A runbook
Written steps for the things that go wrong, so your team is not blocked waiting on us.
Support is a retainer, not an open-ended promise. What is covered and what is billed separately is written down before it starts.
Need someone to hold the pager?
We take on systems we did not build, once we have read the code and said so honestly.