At 2M queries/mo our list pricing is $8 (https://nsone.net/support/billing/). Indeed our Biz Plan is $200 -- but that includes 24/7 support, 25M queries, and other bells & whistles. If you just need a little more volume, stick with the startup plan.
That said, indeed, in general we're more expensive than R53, Rage4, and various others, because of the depth of capabilities of the platform and the quality of the support we provide. But we're also pretty unique in giving away 1M queries free with no feature locking, so our most advanced stuff is available to everyone. If you're just after basic geo-routing at the lowest cost, we're happy to help but you may find other services cheaper; but if you intend to go beyond geo to complex failover arrangements, load shedding, weighting/stickiness, network-based fencing, etc, then do some tinkering with NSONE and let us know what you think. Feedback is always good. :)
Fair enough, I just glanced at the pricing pages. As this is intended for something that is ultimately a hobby of mine, it is more price sensitive than feature/support sensitive.
If I was trying to make a living at it, I'd seriously consider you even at $200/month.
The reason for my joy at the R53 news is the fact that w/o Geo it'd be worthless to me.
At 2M queries/mo our list pricing is $8 (https://nsone.net/support/billing/). Indeed our Biz Plan is $200 -- but that includes 24/7 support, 25M queries, and other bells & whistles. If you just need a little more volume, stick with the startup plan.
That said, indeed, in general we're more expensive than R53, Rage4, and various others, because of the depth of capabilities of the platform and the quality of the support we provide. But we're also pretty unique in giving away 1M queries free with no feature locking, so our most advanced stuff is available to everyone. If you're just after basic geo-routing at the lowest cost, we're happy to help but you may find other services cheaper; but if you intend to go beyond geo to complex failover arrangements, load shedding, weighting/stickiness, network-based fencing, etc, then do some tinkering with NSONE and let us know what you think. Feedback is always good. :)