Depends on your region - check the frequency plans page in the docs - and consider that in some regions it may be supported but you may be the only one using it.
No public LoRaWAN network supports moving gateways and we particularly ask that they are not connected to TTN - the GPS is irrelevant, it only tells you where it is, which you know because you put it there - and what the time is - which is irrelevant as it is connected to the internet. If you setup a gateway and other peoples devices are heard by it, the LNS may well adjust settings based on the gateway, which when it disappears, will leave the devices out of range until they do a connectivity check.
To be clear, a gateway that’s moving that is on TTN is a form of denial of service to the community. So please don’t.
Depends. If your CS server is on your home network, no, but then that’s a bit obvious. If you host externally, it is deeply unlikely you will be able to replicate the finely tuned set of services and the raw horsepower that TTI provide.
However the latency of an uplink is not a thing - arriving inside 5ms or inside 25ms is totally academic for LoRaWAN which is not about command & control response times. I hit the test button on a device on my desk and my web browser shows me the information faster than I can move my eyes …
Yes, the FUP is as much about the use of the backend servers as not destroying the local airwaves with overly enthusiastic devices. But if you have a gateway and you have a device that needs more than 30 seconds air time a day, it’s likely to be a questionable use for LoRaWAN, even if the private legal limits would allow you far more uplinks.
Not if the gateway is on TTN.
A device has to be registered on an LNS and you need a gateway to relay the radio waves to the LNS, so you will need a gateway for your local nodes for the ‘unlimited personal devices’ which are an element you may need to explain - a node is a device is a MCU+radio+ sensors. And unlimited varies for corporate deployments in the hundred of thousands to five for your local techno-granny monitoring cat bowl weights.
Whilst you are deploying the unlimited low latency personal devices, you may want to factor in the local legal regulations.
Overall, get stuck in, but get one gateway and two or three devices setup so you’ve more context to your LoRaWAN adventures.
Many users like to concentrate on the devices & the dashboard / reporting and leave the LNS challenges to someone else. So please bear in mind that this forum is funded by TTI, so Chirpstack help isn’t available here.