What this package is
Harden is for systems where a mistake costs money. It covers taking payment so that if the bank reports the same one twice, nobody is charged twice, which a great many systems get wrong because every provider repeats a notification when a connection stumbles.
It moves heavy work into the background so nobody sits waiting, holds off bursts and floods so the system stays up, and logging with alerts when something goes wrong.
It finishes with a security review of the system I am about to hand you, run with the same tooling I use for clients in the security service, delivered with the findings and what was already fixed.
See it working
The first one causes the most damage when it is missing. Every payment provider repeats a notification when a connection stumbles. A system not built for it records two orders and charges twice.
This mirrors the screen of the delivered system. Everything here lives in this page and is connected to no bank and no system. All three are things I have built against real money, and a security review is attached to the work at handover.
Everything you get
This list is the entire scope of the package. Nothing is hidden in a contract.
- Everything in Admin
- Takes payment, and if the bank reports the same one twice it is not charged twice. One payment provider connected.
- Heavy work runs in the background, so nobody sits watching a screen
- Bursts and floods are held off, so the system stays up for everyone else
- The monthly summary sent to you by email, so nobody has to remember to open it
- An immediate alert when a figure looks wrong, up to three conditions you choose
- Logging and alerting when something goes wrong
- A security review of the system I am handing you
- 60 days of support after handover
- Front-end design and build. This service covers only what sits behind it. If you need both sides, look at the business website or the booking system, which ship with a front end.
- Monthly server and third-party costs, paid from your own accounts so the system genuinely belongs to you. I estimate the figures before we start.
- Migrating data out of an old system with a complicated structure. Ordinary spreadsheets I move for free; pulling through a legacy API is quoted separately and told to you first.
- Mobile apps. That is the Android service, which can call the API built here.
- A registered company on my side. I am one developer working under my own name in Thailand, and the contract is with me personally.
Questions about this package
How do you stop a repeated call charging twice?
Every money-related request carries an identifier. The system remembers which identifiers are done and returns the original result rather than repeating the work. It sounds simple; where people get it wrong is deciding at which layer to remember and for how long, which I have already worked through on systems handling real money.
How is the included security review different from your security service?
This one reviews the system I have just built, before handover, and covers what I wrote. The separate service reviews systems built by others or already in production, which is broader and includes testing from outside.
Do background jobs need another server?
Usually not. At this size a queue service with a free tier is enough. If volume grows past that I give you the figure in advance, and it is a third-party cost paid from your own account rather than mine.
If it goes down at three in the morning, who is watching?
This package makes the system able to raise an alert. It does not include somebody watching around the clock. For ongoing cover after handover, that is the monthly care service. I keep them separate so you are not paying for monitoring inside a one-off price.
Why buy this if it already works from the first package?
If your system does not touch money and traffic is modest, the first or second package really is enough and I will say so. This one exists for when a single mistake has a price: charging twice, going down as a sale opens, or leaking customer data. All three cost far more to fix afterwards than to prevent.