@swearyanthony I've found Hugo (https://gohugo.io/) paired with one of the services that can publish your site in response to git commits pretty good (e.g Netlify, Github Pages, Gitlab Pages, or I guess even AWS Amplify now).

It won't give you comments, but is low cost (perhaps just the cost of your domain) and has a decent number of ready made themes available.

@decryption Maybe?

I guess it might be good enough if there is doubt about whether counterfeit stamps will be accepted.

There'd also be a limit to how complicated it is worth making the security features. Unlike a bank note that will be reused hundreds or thousands of times, a stamp is used once.

@decryption There's still lots of room for screwing people over.

If you bought a roll of 50 stamps, would you unroll it and check every stamp for authenticity? Or would you check the first few and assume the rest were okay?

If a counterfeiter put 5-10 valid barcodes at the beginning of a roll and dummy ones after, would you notice? Or if they took a full set of barcodes and printed them in reverse order on a second set of stamps: they'd almost all appear valid at first, but you'd run into problems ~ half way through.

@decryption It looks like the UK has done so with a barcode section on the stamps now:

https://www.royalmail.com/sending/barcoded-stamps

I'm still not sure how a regular person could tell whether a particular barcode has already been used as postage.

@decryption At some point, they'll probably have to put a unique serial number + digital signature on each stamp. Counterfeiters might be able to copy the serial number, but it'd be possible to see if a number has already been used for postage.

That'd still leave the problem of regular people not being able to tell the difference though, so isn't a complete solution.

@decryption Better than the sign that was on one of the local post boxes here.

It informed people that if they'd posted mail in that box on a particular day, they should consider reposting it again because the the box had been set on fire.

@merospit @davidgerard That page shows prices ranging from $0.10 to $40 for a million input tokens depending on what model it is for.

If the number of tokens processed is meant to be a proxy for revenue, which price are you meant to use?