Skip to content
Audixa
Audixa

Service

A web product or a mobile app, built the way this scanner is built

We build web applications and, when the product needs to live on a phone, mobile apps — the same way this one is built: authorization checked on the server for every request, tenant separation enforced by the database rather than by remembering, secrets that never reach the browser, and an audit trail for anything that changes access. That is not an add-on at the end of the project. It is most of what makes the difference between an application that works and one that is safe to put customers on.

Tell us about your project

A person reads it and replies, usually within two working days.

What it costs

Fixed price per phase, quoted after the scoping conversation. Not hourly: an hourly rate makes our incentive the opposite of yours, and it makes the total unknowable at the point you have to decide. If a phase turns out to be larger than we scoped, that is our estimate that was wrong.

Who it suits

Three situations this is for

  • You have a prototype and need the real thing

    Something built quickly that proved the idea and now has to hold real customers, real money and real data. The rewrite is usually smaller than you fear and the parts that must change are usually not the ones you expected.

  • Your product handles other people's data

    The moment one customer's records sit next to another's, access control stops being a feature and becomes the foundation. It is also the single most common place a fast-built application is wrong.

  • You need to answer a security questionnaire

    Selling to a company with a procurement process means being asked how access is controlled and what is logged. Building with those answers in mind is dramatically cheaper than retrofitting them.

How it goes

The engagement, step by step

Written out because the thing people actually want to know before sending an enquiry is what happens next, and how easy it is to stop.

  1. A scoping conversation, before any estimate

    An hour or two on what the product does, who its users are, and which data must never leak between them. We charge nothing for this and we will tell you if we think the project does not need us.

  2. A written scope with a fixed price per phase

    Broken into phases you can stop after. Each phase names what will exist at the end of it and what it costs, so the decision to continue is made with something working in front of you rather than on faith.

    If we cannot describe a phase in a paragraph, it is too big to price.

  3. We build in the open

    Your repository, your infrastructure accounts, commits you can read as they happen, and a working deployment from the first week. You are never waiting for a reveal.

  4. Review, handover, and a clean exit

    A security review of what we built, the architecture notes, and a handover to whoever takes it on. The measure of the engagement is whether another developer can pick it up without calling us.

    Maintenance afterwards is optional, and it is a separate arrangement.

What you end up with

  • A working application, deployed, with the repository and the infrastructure in your accounts
  • Authorization enforced server-side on every route, and a test suite that tries to read another tenant's data and expects to fail
  • Written architecture notes: what the boundaries are, why they are where they are, and what will break if they move
  • A security review of the finished product, which is what we do anyway, run before launch rather than after
  • A handover session with whoever will maintain it, recorded if you want it

Boundaries

What this does not include

Better to find the edge here than after an invoice.
  • We do not start building from a one-line brief. If the scope will not survive being written down, the estimate is fiction and the project will end badly for both of us.
  • We do not take equity instead of payment, and we do not build for a share of revenue.
  • We do not silently assume ongoing maintenance. Handover is designed to be a real exit, and continuing is a decision you make separately.
  • Building securely reduces risk. It does not eliminate it, and no engagement with us comes with a guarantee that your application cannot be broken into.

Questions

About custom web or app

What do you build with?

TypeScript, React and Next.js on Postgres, which is what this product is built with. We are not dogmatic about it, but we are honest that a stack we know deeply is where we are fastest and most careful — and if your project genuinely suits something else, we would rather say so than learn it on your budget.

Can you work alongside our developers?

Yes, and it is often the better arrangement. What we ask for is a clear boundary about who owns which part, because two teams both assuming the other checked authorization is a specific and common way for this to go wrong.

How long does a project take?

We answer that per phase after scoping, and not before. A number given before we understand the data model is a guess, and a guess given confidently is worse than no answer.

Send an enquiry

Tell us about your project

Enough detail that we can give you a real answer rather than ask for a call to find out what you meant.
No obligation, no automatic charge

Sending this does not commit you to anything and does not start any billing. You will get a confirmation with a reference straight away, and a reply from a person after that.

Incluye el prefijo del país, por ejemplo +34.

Opcional.

Opcional. Nos ayuda a revisar tu infraestructura previa.

Qué tienes, qué necesitas y los plazos previstos. Unas pocas frases son suficientes.

Opcional.

Un especialista lee cada solicitud. Recibirás una confirmación con número de referencia de inmediato y una respuesta técnica personalizada. No hay cargo automático.