Kitchen Table Talk

Third option nobody lists: kysely. Typed query builder, no migration engine, no opinions, tiny. You bring your own migration runner, which for two people is a folder of .sql files and thirty lines of node.

The detail that changes the answer for a lot of people is where the allowance can be spent. Plans steer you to in-network providers and pay much less, or nothing usable, when you buy from an online retailer, so the headline frame allowance is not money you can take to the cheapest seller. Read the out-of-network reimbursement line specifically. Mine reimburses a fraction of what it pays in-network, which made the whole plan pointless for how I actually shop.

So the increase is the market rather than my file. That is oddly reassuring and also more annoying.

Fixed 512 with 64 overlap is a perfectly respectable baseline and takes an hour. Heading-aware is better when the headings are reliable, which for machine-generated equipment manuals they usually are and for scanned ones they are not at all. Do the cheap version, measure, then decide whether the parsing code is worth it.

For £2,000 of replaceable stuff and no liability worry I'd self-insure. The liability point above changed my mind for the flat I'm in now, which has a bathroom sitting directly above somebody's kitchen.