I'd say that for any non-toy service, the default is that you do need those things, and would probably be helped by a database that cares what type you said the column had
Can you even redeploy a sevice like this without downtime?
Do you need to redeploy your service without downtime?
Do you need multi-user and remote access?
Why can't you just use a copy of the database when you need to examine it or resolve issues?
None of these things have anything to do with being a "toy" app or not. They are matters of scale and business requirements. But that's the point isn't it? There are plenty of non-toy systems where none of these requirements apply.
Plenty of very successful business and applications could handle a brief downtime for deployment. Plenty don't need multiple users or remote access, plenty have reasonably small databases.
Can you even redeploy a sevice like this without downtime?