Interestingly, I think we're seeing less people grow up with general purpose computers, and instead just have an iPad or an android tablet, or a chromebook.
Not the OP, but the people I've seen this do it DIY have all done it with Ubiquiti products. A single link can get a mile of range with clear LoS. Depending on how far out you are, that lets you connect to a "real" internet connection for cheap.
One thing you may encounter is that a large company may be using it for many things internally, and that still shows up as just a handful of clones, because they have some central artifact caching service in place.
Essentially this is a way to lets you push all of the weird feature requests your customers might have off into one place.
From a customer point of view, maybe you need to rewrite the path based on the contents of a cookie, or maybe you want to shed certain types of requests in high load scenarios, or maybe there's a buggy upstream application that sends bad cache-control headers, or ...
If the goal is to let the customer specify infinitely complex logic at the edge, a programming language is a good way to do that. Function As A Service is a good billing model for lots of invocations of short, small functions across the customers choice of language.
Why not start out by using the Django Admin features?
That allows you to start with next to no code, but you can easily add a little business logic anywhere you need it eventually, and it provides a way to long term transition to a true application if the need arises.
In a series of calls with the top tier of support at Paypal, no one was able to even answer which API was the best to use. I was told not to use SOAP (or NVP), because they're ancient, not to use REST because it wasn't ready yet, and that the Braintree API around PayPal would never support the features we were trying to implement.