I take source control advice from people who are bigger freaks about robustness than I am. But I will always remember Zed as the guy who took a straw poll (of English speakers!) about whether it would be okay to drop email on the floor if his server didn't understand its text encoding. So, no.
It's a one file install. You can easily run it behind firewalls. It has built-in wiki and issue tracking. You can run it from a jailed host; it requires no access to apache config, it has its own server. You can give users accounts on it. You can run it in autosync mode, where everyone's changes are sync'd through a central repo, or you can use manual merge for disconnected use. It uses the battle-tested sqlite as its transactional local store. It is designed to optimize the author's preferred workflow, so if you agree with him in principle, you'll like its ui. Like, e.g., git, it uses SHAs for "artifact" tracking; the sqlite db can be rebuilt from the canonical artifacts. I haven't looked for any comparisons, but it's extremely efficient space- and bandwidth-wise. It's written in SQL, which is semantically efficient, so it's easy to understand how it works.
