I expect a minimal web-application server to do two things: serve semi dynamic html pages provide an API interface to web-based client Very simple HTTP-based API You can create your API-s in plethora of ways, but I mostly used a very simple strpc "standard" to do my API-s for the last 14 years. It's very easy to create and serve an API on the server side and it's very easy to call such API. Any programming language, or a bash shell can do it without any special libraries. I called it strpc (SoTinyRPC) back then. In short, a HTTP POST request to url like this: www.example.com/API?_r=util&_m=add with url-encoded arguments in a POST payload: a=100&b=11 ... would be an example of strpc call. _r - defines resource _m - defines method _f - (optional) would define response format (json, csv, html, ...) _x - (optional) would define explore mode (api self-documents itself) You can make a strpc call from your shell using Curl command, for example: curl -k \ -u $T...