@takahe do you have any kind of numbers on suggested "hardware" specs?
@astraluma That's a tough one - probably 2GB of RAM plus whatever a virtual CPU core is these days, split between the webserver and the background worker. Have heard of it fitting all in 1GB, though not without occasional pains.
@astraluma The advantage of a relatively tight and new codebase! Plus a good framework and language that make writing decent access patterns easy.
The only real big memory hog is that image resizing is done entirely in-memory, but that generally fits fine within 2GB as images aren't _that_ big.