One-off audits · For SMBs and companies
An outside look at your system, with a report that says what to fix first.
We review cloud costs, the security of AI-written code or performance. In 1 to 2 weeks we measure, find what matters and leave you a prioritised report. The report is yours, whether or not you keep working with us.
01 — What we review
Three audits, each with its own deliverable.
01 · Cloud
Cloud costs
When it makes sense
The bill grows faster than usage, you pay for environments nobody uses, or nobody really knows what each line item is.
AWS, Google Cloud and Cloudflare.
What we review
- Which resources exist, what each one costs and how much it is really used.
- Real traffic by hour, region and endpoint, and the peaks.
- Data transfer, storage and environments running around the clock.
- AI processes: which tasks need it and with which model.
What you get
- A map of the infrastructure with the cost of each part.
- The changes, ranked by estimated savings and effort.
- When to optimise with the same provider and when to migrate.
- The metrics to compare before and after, such as cost per user or per order.
02 · Security
AI-written code
When it makes sense
Part of the system was written with AI, or by someone who is no longer around, and nobody reviewed it thoroughly before it went live.
It also works for code written by other teams or by freelancers.
What we review
- What reaches the browser: sensitive data, keys, internal comments and sourcemaps.
- Who can see what: sign-in, role permissions and admin panels.
- The database: access policies, write permissions and what is left exposed.
- Default credentials, secrets in the repository and internal endpoints.
What you get
- Findings ranked by severity, with the evidence for each one.
- What to fix now and what can wait.
- How to keep it from happening again: code review, tests and checks before every release.
03 · Performance
Performance
When it makes sense
The site or app is slow to load, especially on mobile, or Search Console flags the Core Web Vitals in red.
The gain is often twofold: a well-configured cache lowers the bill and makes the site load faster.
What we review
- Core Web Vitals on mobile and desktop, with real-user data when there is some.
- Images, videos, fonts and third-party scripts: what weighs and what loads too early.
- Server response times and slow database queries.
- Caching and the CDN.
What you get
- A plan of independent tasks, ranked by impact and risk.
- The baseline measurement, to compare after each change.
- What can be solved without touching the code and what needs changes.
02 — How we work
From the call to the report, in 1 to 2 weeks.
30-minute call
You tell us what worries you and we tell you which audit makes sense, or whether you need one at all.
Proposal
We send you the scope: which systems we review, what access we need and when we deliver.
Review and measurement
We work without slowing down your operation. If we find something serious, we tell you right away, without waiting for the report.
Report and walkthrough
We present the report in a meeting with your team and answer questions.
What is clear from the start
- The report belongs to your company, whether or not you keep working with us.
- Each finding comes with its evidence and what to fix first, in language both the tech team and management understand.
- We sign a non-disclosure agreement if your company needs one.
- If you want us to make the fixes, we quote them separately and in stages. It is not a condition.
03 — Cases
We apply it to our own products.
EdTech app · Cloud costs
Estudiantino
Before launch we moved from Vercel to Cloudflare and fixed infrastructure costs dropped by 80%.
See the case →AI web app · Performance and security
gambeta.ai
The audit produced a 10-task plan: mobile PageSpeed went from 37 to 92 and LCP from 12.4 s to 1.2 s. We also locked down more than 30 internal endpoints and replaced the admin PIN with roles.
See the case →
These are products we build and run. We'll add client audits soon, once clients let us tell them.
04 — FAQ
Frequently asked questions
What access do you need?
It depends on the audit. For performance, the public site is usually enough. For costs, read access to billing and the cloud console. For security, the code and the configuration. We agree on it in the proposal.
Does it slow down our operation?
No. We review and measure without changing anything in production. If a test could affect users, we run it in a test environment or at a time we agree on.
Is it a penetration test?
No. We review the code, the configuration and what is published. If a formal penetration test is needed, we say so in the report.
Who fixes what you find?
Your team, with the report in hand, or us, if you prefer: we quote it separately and in stages.
Does it work if you didn't build the system?
Yes, that's the most common case. We review systems built by other teams, by freelancers or with AI tools.
Can audits be combined?
Yes, and sometimes it's worth it: costs and performance often share causes. We define it in the proposal.
Do you work with companies outside Argentina?
Yes, in Spanish or English, over video call.
What do you want to review first?
Book a 30-minute video call or tell us what worries you and we'll get back to you within 24 hours.