A couple of things:
1) Why do you not use React Router? How does your own router play with Redux?
2) Is it possible to strip out now.sh? I appreciate it's how you make money but I want to deploy to my own infrastructure.
To answer your questions:
1) Because the router in next.js embeds really well into the model of pages, prefetching, etc. while still keeping the mechanisms simple, here's how to use with redux: https://github.com/zeit/next.js/tree/master/examples/with-re... 2) now.sh is in no way mandatory. To deploy anywhere, `next build` and `next start` will run the node.js server, so you're free to deploy it anywhere you'd like: https://github.com/zeit/next.js#production-deployment
We currently use global state at https://zeit.co to keep the authenticated user in memory without re-checking for every page transition.
You can think of Next.js's Router as a "strict subset" of RR. Definitely possible for us to simplify our codebase by switching to RR in the future.
2. Nothing about this framework is dependent on now.sh. We, however, did design now.sh to make deployment of applications as this as easy, fast and scalable as possible with collaboration in mind.
tl;DR: You can do any sort of routing! We use a /:org/:project scheme similar to GitHub at https://zeit.co :)
Some examples:
- https://github.com/zeit/next.js/tree/master/examples/paramet...
- https://github.com/zeit/next.js/tree/master/examples/with-ne...
- https://github.com/zeit/next.js/tree/master/examples/with-pr...