Spokane companies needing disaster recovery don't need a second cloud contract. IDACORE North, 2115 N Government Way in Coeur d'Alene, is a live facility 45 minutes from downtown Spokane offering per-U and cabinet colocation at $300/kW/month—identical pricing to Boise, open for orders now.
Why Does DR Distance Actually Matter?
Disaster recovery planning has a distance problem most people don't think through until it's too late. Put your DR site too close to production and a regional event—a windstorm, a substation failure, a fiber cut on the wrong trunk—takes both down together. Put it too far and your replication lag turns into a real RPO problem, and your team never actually drives out to touch the hardware when something goes sideways.
Coeur d'Alene sits in the sweet spot for Spokane. It's on a different power grid, different last-mile fiber paths, and outside the blast radius of anything that would take out a Spokane data center. But it's still a 45-minute drive. That's close enough that your ops team can be on-site same-day for a hardware swap, a manual failover, or just to eyeball a cabinet during a change window. Try that with a DR site in Denver or Dallas.
We've run infrastructure in this region for 30 years. We know what actually knocks out power and fiber here versus what's theoretical risk from a compliance checklist. Coeur d'Alene and Spokane don't share a substation. They don't share carrier hotels. That's the redundancy that matters, not just a different zip code on paper.
What Does Regional Redundancy Cost at IDACORE North?
Here's where the second-cloud-bill problem comes in. Most companies handling DR through a second AWS or Azure region end up paying full compute and storage rates in that region, plus egress fees to sync data between regions, plus the complexity of managing two cloud environments with two sets of IAM policies, two sets of monitoring, two invoices that never quite reconcile.
IDACORE North runs at the same $300/kW/month as Boise, billed on actual power draw. A DR deployment that idles most of the year—say a standby database replica and a couple of application servers pulling 800W combined—costs $240/month. Compare that to running an equivalent standby environment in a second cloud region where you're paying for reserved instances or, worse, forgetting to scale them down and eating the bill anyway.
| Approach | Monthly Cost (approx.) | Egress Surprises | Physical Access |
|---|---|---|---|
| Second cloud region (AWS/Azure) | $600–1,200+ (compute + storage + egress) | Yes, scales with failover volume | None |
| IDACORE North (800W standby) | $240 (power only) | No, flat transit pricing | 45 min from Spokane |
| IDACORE North (2kW active-active) | $600 | No | 45 min from Spokane |
The math gets better as you scale. A 5kW DR footprint runs $1,500/month flat. No egress line item creeping up every quarter because your replication job ran longer than expected.
What About the Network Path?
IP transit at IDACORE North is priced the same as everywhere else we operate: committed bandwidth, 95th percentile billing, on our own ASN. A 1G commit is $450/month ($0.45/Mbps). If your DR site needs to replicate continuously to Spokane or beyond, you're looking at predictable transit costs instead of a cloud provider's per-GB egress meter running in the background.
We peer this traffic ourselves. No reselling somebody else's transit contract and marking it up. When there's a routing issue between Coeur d'Alene and your Spokane office, we're the ones who can actually do something about it—not a support queue reading a runbook.
What Compliance Does IDACORE North Support?
DR sites for regulated workloads need more than proximity—they need certifications that hold up in an audit. IDACORE's compliance posture (SOC 2 Type II, PCI DSS, NIST 800-53, SSAE-16, HITRUST CSF) applies across our Idaho facilities, and North is compliance-ready for HIPAA, financial services, and government workloads. If your primary site in Spokane or Seattle handles patient data or financial records, your DR site needs the same audit trail, not a lesser standard because it's "just backup."
Data residency is part of this too. Everything at IDACORE North stays in Idaho—it doesn't cross state lines, which matters if your compliance framework or contracts specify data locality. That's a harder guarantee to make with a cloud region where the provider controls the physical location and can shift capacity without telling you.
A Real Scenario: Spokane Healthcare SaaS Firm
Take a healthcare SaaS company running production in a Spokane-area data center serving regional clinics. Their compliance requirement: an out-of-region DR site with equivalent security certifications, RPO under 15 minutes, and RTO under 2 hours. Their first instinct was a second AWS region—until they priced out cross-region replication for a database doing 200GB of daily change volume. Egress alone was pushing $3,000/month before compute.
They moved DR to IDACORE North instead. A 3kW standby footprint (replicated database, app servers, load balancer) runs $900/month in power, plus a 1G transit commit at $450/month for replication traffic. Total: $1,350/month, flat, predictable, and HIPAA-compliant on facility certifications they already had documentation for. Failover testing happens quarterly, and their ops lead drives up from Spokane when they need physical hands on the rack.
Frequently Asked Questions
How far is IDACORE North from Spokane, Washington?
IDACORE North sits at 2115 N Government Way in Coeur d'Alene, Idaho, approximately 45 minutes by car from downtown Spokane. That distance provides genuine grid and infrastructure separation for disaster recovery while staying close enough for same-day physical access.
What does colocation cost at IDACORE North?
IDACORE North bills colocation at $300/kW/month based on actual power draw, with no minimum power commitment and a 1U minimum footprint. A 1kW deployment costs $300/month; a 5kW DR environment runs $1,500/month, flat and predictable.
Is IDACORE North compliant for HIPAA and financial workloads?
Yes. IDACORE North is compliance-ready for HIPAA, financial services, and government workloads, backed by SOC 2 Type II, PCI DSS, NIST 800-53, SSAE-16, and HITRUST CSF certifications shared across IDACORE's Idaho facilities.
How does IP transit pricing work for DR replication traffic?
IP transit is committed bandwidth billed at 95th percentile on IDACORE's own ASN. A 1G commit costs $450/month ($0.45/Mbps); a 10G commit costs $1,350/month ($0.135/Mbps). There's no per-GB egress fee, so replication volume doesn't create surprise bills.
Can I use IDACORE North without a Boise or East deployment?
Yes. IDACORE North operates independently and is open for active orders now—per-U and full cabinet colocation, no dependency on Boise or the Eastern Oregon build. Many customers use it as a standalone DR site for production infrastructure elsewhere in the Pacific Northwest.
If your DR plan still depends on a second cloud region and a monthly egress surprise, it's worth pricing out what a 45-minute drive from Spokane could save you—talk to our team about a DR deployment at IDACORE North and get real numbers based on your actual replication footprint.
