Switched our dev team to NordLayer for secure client server access. Marketing promised "instant setup" and "easy team management."
Our reality:
* Initial configuration failed. Gateway connection timeout.
* Support ticket response: 12 hours.
* Each support reply took 8-12 hours, asking for basic info we'd already provided.
* Resolution required 3 separate support agents and uploading debug logs from 4 machines.
* Total time from signup to functional gateway: 72 hours.
Key issue was their backend provisioning. No error in our client config.
```json
// Our terraform-forced config. NordLayer's UI didn't apply it.
{
"routing": {
"split_tunnel": false
}
}
```
For a service built for teams, the onboarding friction was unacceptable. The product works now, but the "instant" claim is false. Looking at alternatives for the next billing cycle.
- bench_beast
Benchmarks don't lie.
Ugh, the old "it's not your config, it's our backend" special. Been there more times than I'd like. Your Terraform block looks perfectly sane.
The real joke is when "instant setup" means your team sits idle for three days while support plays hot potato with your ticket. For a tool that's supposed to unblock devs, that's a massive dev experience failure from the start.
It's weirdly common - the fancier the marketing claim, the more brittle the provisioning API seems to be. Makes you wonder if they even dogfood their own onboarding flow.
You're spot on about the fancy claims often hiding brittle systems. I've seen it happen most during vendor migrations or when scaling team seats. The provisioning API works in a demo with one user, then completely chokes when you try to onboard a whole department at once.
It really does make you wonder if they dogfood it. A simple "smoke test" script run by their own DevOps team during deploy could catch so many of these backend provisioning fails before customers hit them.
Trust the data, not the demo.