Software engineering & AWS
Software that ships.Infrastructure that holds.
We build web and SaaS products, and we run the AWS they live on. One team for both halves, so the thing we build is the thing we keep running.
Not sure whether your problem is the code or the cloud? That question is usually the answer — describe what is going wrong and we will work out which half it is.
Most projects put a vendor boundary on that spine. We do not, which is why the architecture and its running cost get decided together.
What we do
- Software EngineeringWeb apps, SaaS platforms, APIs and internal tools
- Cloud & AWSArchitecture, migration, security and cost on AWS
- DevOps & PlatformCI/CD, infrastructure as code, environments, observability
- Data & IntegrationsPipelines, reporting, payments and event-driven systems
- Managed SupportOngoing engineering, monitoring and incident response
01/Why both halves
Most vendors sell you one half of the problem.
An agency builds the application and hands over a repository. A cloud consultancy inherits infrastructure somebody else designed under different assumptions. Both are doing competent work, and the gap between them is where the expensive problems live.
The architecture gets chosen by people who will not operate it. The running cost is discovered on the first serious invoice rather than decided while it was still cheap to change. And when something breaks at 3am, the first fifteen minutes go on working out whose side of the line it is on.
We do both. Not because it is a broader offering, but because it removes that line from the project entirely.
What that changes
- TypicalThe application is designed, then somewhere to run it is found.
- HereThe architecture and its running cost are decided together, before either is expensive to change.
- TypicalAn incident starts with two vendors establishing whose fault it is.
- HereOne team owns the request from the browser to the database, and starts by fixing it.
- TypicalHandover is a repository and a diagram that stopped being true months ago.
- HereHandover is a runbook, infrastructure as code, and your engineers making a change while we watch.
02/Solutions
Start from the problem you actually have.
- 01/Build a new productYou need to build something, and it needs to actually run.A working product in production, with the pipeline and infrastructure to keep shipping it.
- 02/Migrate to AWSMoving to AWS without the weekend everyone dreads.Each workload moved in a reversible step, with the cutover rehearsed before it is real.
- 03/Modernize legacy softwareThe system still works. Nobody wants to touch it.The same system, still running, that your team can now change without holding its breath.
- 04/Reduce cloud costsOur AWS bill doubled and nobody knows why.A line-by-line account of where the money goes, and the specific changes that reduce it.
- 05/Scale and performanceIt gets slow, and we keep buying bigger servers.The real bottleneck identified and fixed, with headroom you can measure.
- 06/Secure your infrastructureA customer started asking security questions.A reviewed environment, the gaps closed in priority order, and answers you can evidence.
03/How we work
Five steps, and none of them is a discovery maze.
You tell us what you need
A reply from someone technical within one business day.
We look at it properly
An informed opinion rather than a generic one.
We propose an approach
A scoped approach with the assumptions and exclusions written down.
We build it in increments
Working software in an environment you can use, updated as we go.
We hand it over
A repository, a runbook, an architecture document and a recorded walkthrough.
04/What we work with
The tools, named.
No badges and no partner logos. This is what we actually write and operate, and we will tell you when your problem needs something that is not on it.
- Languages
- TypeScript
- JavaScript
- Python
- SQL
- Frontend
- React
- Next.js
- Tailwind CSS
- Backend
- Node.js
- FastAPI
- Django
- REST
- GraphQL
- AWS compute
- Lambda
- ECS
- Fargate
- EKS
- EC2
- API Gateway
- AWS data
- RDS
- Aurora
- PostgreSQL
- DynamoDB
- S3
- ElastiCache
- AWS platform
- VPC
- CloudFront
- Route 53
- IAM
- CloudWatch
- EventBridge
- DevOps
- Docker
- GitHub Actions
- AWS CDK
- Terraform
- CloudFormation
- Testing
- Vitest
- Jest
- Playwright
- pytest
Tell us what is going wrong.
A few lines is enough to start. You will get a reply from an engineer, not a sales sequence, within one business day.