01 · Connect
Create a read-only IAM user with the policy SpendGuard publishes and paste in its keys. No agents, no CloudFormation stacks, nothing to deploy.
Products
Software we build and run
We don’t only advise on infrastructure — we ship products on top of it. Each one runs on the same practices we recommend to clients.
AWS cost control
SpendGuard
Stop paying for cloud resources you don’t use. SpendGuard scans an AWS account with read-only access and shows exactly which idle and orphaned resources are costing money — with the command to fix each one.
Forgotten dev boxes, volumes left behind by terminated instances, load balancers with nothing behind them: none of it raises an alarm, it just stays on the bill. SpendGuard puts a monthly figure on each one so the clean-up is a short list rather than an audit.
About five minutes
From read-only keys to a list of fixes
02 · Scan
Nine scanners check ten AWS regions for idle compute, orphaned storage and networking you no longer use. A full scan typically takes a couple of minutes.
03 · Fix
A prioritised list with a monthly cost for every finding, the reason it was flagged, and the AWS CLI command that removes it. You decide what to run.
Coverage
Nine scanners for the most common AWS waste
- Unattached EBS volumes
- Idle EC2 instances
- Idle RDS instances
- Orphaned snapshots
- Unused Elastic IPs
- Empty load balancers
- Low-traffic NAT gateways
- Stale S3 multipart uploads
- Unused Lambda functions
Read-only by design
SpendGuard only calls Describe, List and Get APIs, under an IAM policy you grant and can revoke at any moment. It cannot create, modify or delete anything in your account: fixes are commands you review and run yourself. Cost estimates use published AWS on-demand list prices, so they are a close guide rather than an invoice.
One AWS account is free, with all nine scanners. Pro adds unlimited accounts, automated nightly scans and a weekly savings report by email.
Healthcare operations
iVerify
Insurance verification, simplified. iVerify turns payer coverage calls into structured, reviewable verification records without losing human oversight.
Chasing eligibility on the phone is slow, and what was said tends to survive only as a note someone typed afterwards. iVerify keeps the submitted facts, the payer conversation and the final human decision connected to one case from start to finish.
One accountable workflow
From intake to completed verification
01 · Capture
Staff submit only the subscriber, provider, payer, and CPT details that need verification — a controlled source of truth for the call.
02 · Call
A queued voice workflow follows the payer’s required sequence, limits confirmation to the submitted case details, and records the answers it receives.
03 · Review
A person confirms the result, resolves exceptions, and approves the record. Call evidence never becomes an approved verification on its own.
Built for daily operations
Every result stays attached to the case
- Attempt history, payer routing and collected responses stored with the case
- Operators, reviewers and administrators get different actions and views
- Organisation users see their own records; administrators can see across tenants
- Completed verification form downloadable from the same workspace
Current status
iVerify is a working model demonstrated with synthetic records, and sign-in is limited to invited users. A production rollout adds the customer’s own identity, compliance and infrastructure controls — managed SSO, audited authorization, encryption and key management, retention policies and monitoring.
If that is a problem you have, we would like to hear about it.
Why it sits here
The same practices we sell, on our own systems
iVerify runs on infrastructure defined in code, deployed through a pipeline, and monitored the way we would set it up for a client. Tenant separation, role boundaries and audit trails are architecture decisions, not features bolted on at the end.
It is the most direct answer we can give to a fair question: does the person advising us actually operate anything?
Infrastructure as code
The environment is described in Terraform and rebuildable from the repository.
Boundaries by design
Role separation and tenant isolation decided up front, not retrofitted.
Infrastructure automation
The Inframodule app
The tool we use to automate infrastructure work: the same provisioning, deployment and operations tasks described on this site, run from one place instead of by hand. Access is by account, created by an Inframodule administrator for the teams we work with.
Have a problem that looks like one of these?
An AWS bill nobody can fully explain, or a workflow stuck on the phone with no audit trail. Tell us what it looks like and we will tell you honestly whether we can help.