You can meet data residency requirements for a Spokane-area DR site by colocating at IDACORE North in Coeur d'Alene, Idaho — 45 minutes from Spokane, open for active orders today. Power runs $300/kW/month, identical to Boise, with data staying in Idaho at all times, satisfying residency clauses that many cross-border DR plans quietly violate.
Why Does Your DR Site's Location Matter for Compliance?
A lot of DR plans get built backwards. Someone picks a facility based on price or availability, and only later does the compliance team ask where the data actually lives. If you're a Washington-based company replicating data to a DR site in another state — or worse, another country via a hyperscaler region — you may have already broken a residency requirement you didn't know applied to your DR copy.
Data residency rules don't stop at your primary systems. If you're under Washington state contracts requiring data to stay within US borders, or you're handling health records under HIPAA, or you're a financial services firm with state-specific data handling rules, your backup and DR replicas are subject to the same requirements as your production data. A DR site that solves your availability problem but creates a compliance problem isn't a solution. It's a liability with a different name.
This is where geography does real work. IDACORE North sits at 2115 N Government Way in Coeur d'Alene, Idaho — close enough to Spokane to serve as a practical, low-latency DR target, but far enough to give you genuine geographic separation from a Seattle-side seismic or wildfire event. Data replicated between a Spokane primary and a Coeur d'Alene DR site never crosses a state line. It stays in the Pacific Northwest, inside Idaho, the whole time.
How Close Is Coeur d'Alene to Spokane, Really?
About 45 minutes by car, and that proximity matters for two separate reasons: recovery time and compliance posture.
For recovery time, 45 minutes puts IDACORE North close enough for hands-on DR work — swapping drives, walking a rack, meeting a vendor for hardware delivery — without the multi-hour drive you'd face from a DR site in, say, Portland or the Bay Area. If your DR runbook assumes someone might need to physically touch a server, distance is a real operational variable, not an afterthought.
For compliance, the short distance means you get real geographic redundancy without pretending Coeur d'Alene and Spokane are the same seismic zone or the same power grid. They're not. You get separation that satisfies "not the same building, not the same regional disaster" while staying inside a jurisdiction — Idaho — with clear, stable data handling law and no data residency ambiguity.
Compare that to the alternative most Spokane companies default to: replicating into a hyperscaler's nearest region, which might physically sit in Oregon, California, or a us-west-2 zone whose exact location Amazon won't specify in your contract. If your compliance officer needs to answer "where does our backup data physically reside," "somewhere in AWS us-west-2" is not an answer that survives an audit.
What Does This Look Like in Practice?
Take a regional credit union in Spokane running core banking infrastructure on-prem, with a DR requirement under state financial regulations to maintain a geographically separate backup site. Their prior DR contract was with a facility in Denver — technically compliant on distance, but it added 30ms of replication latency and required a flight for any hands-on work.
Moving DR to IDACORE North cut replication latency to single digits, put the DR site a short drive away for their two-person infrastructure team, and kept every byte of member data inside Idaho. Their auditor's question — "where does this data live and can you prove it never leaves state lines" — now has a one-sentence answer with a street address behind it.
What Does Colocation at IDACORE North Actually Cost?
Pricing at IDACORE North matches IDACORE Boise exactly — East is the only site with different economics, because it's built for megawatt-scale AI and HPC, not general colocation. For North and Boise:
| Item | IDACORE North | Typical Cloud DR (hyperscaler) |
|---|---|---|
| Power | $300/kW/month, billed on draw | Bundled into compute/storage pricing, hard to isolate |
| Minimum footprint | 1U, no power minimum | Often none, but egress costs scale with recovery volume |
| Contract term | 12 months standard | Varies, often annual with usage-based true-ups |
| Data location guarantee | Physical Idaho address, verifiable | Region name only, exact facility rarely disclosed |
| IP transit (1G commit) | $600/month, $0.60/Mbps, 95th percentile | Egress billed per-GB, unpredictable at scale |
A 400W DR server at IDACORE North runs $120/month in power (0.4 kW x $300). No power minimum means you can start with a single 1U replication target and scale into a full cabinet as your DR footprint grows — no renegotiation required.
On networking: IDACORE runs its own ASN and BGP peering across all three facilities, so your DR replication traffic between Spokane and Coeur d'Alene rides infrastructure we control end to end, not a resold circuit from a third party. IP transit is priced the same at North as everywhere else — 100M at $170/month up through 100G at $11,050/month, all billed 95th percentile with no egress surprises.
What Compliance Frameworks Does IDACORE North Support?
IDACORE's compliance certifications apply across facilities: SOC 2 Type II, PCI DSS, NIST 800-53, SSAE-16, and HITRUST CSF. That means IDACORE North is compliance-ready for HIPAA workloads, financial services data, and government contracts requiring specific control frameworks — the same certifications backing IDACORE Boise, not a lesser tier for the DR site.
This matters because a lot of DR strategies quietly downgrade their compliance posture at the backup site — "the DR copy doesn't need the same controls, it's just a backup." That reasoning falls apart the moment an auditor or a breach investigation asks about it. Your DR data is still regulated data. IDACORE North treats it that way from day one.
Frequently Asked Questions
Is IDACORE North a good DR site for a Spokane-based business?
Yes. IDACORE North sits in Coeur d'Alene, Idaho, about 45 minutes from Spokane — close enough for low-latency replication and hands-on recovery work, far enough for genuine geographic separation from a regional disaster affecting Spokane.
Does data at IDACORE North ever leave Idaho?
No. IDACORE North is located at 2115 N Government Way, Coeur d'Alene, Idaho. Data colocated there stays within Idaho state lines, which matters for residency clauses in HIPAA, financial services, and government contracts requiring in-state or in-country data handling.
How much does DR colocation cost at IDACORE North?
Power is billed at $300/kW/month based on actual draw, with no minimum — a 400W server runs about $120/month. There's no power commitment minimum and colocation starts at 1U, so you can scale a DR footprint from a single server to a full cabinet as needed.
What compliance certifications does IDACORE North hold?
IDACORE North operates under the same certifications as IDACORE Boise: SOC 2 Type II, PCI DSS, NIST 800-53, SSAE-16, and HITRUST CSF. It's compliance-ready for HIPAA, financial services, and government workloads without a reduced control set for DR deployments.
Can I get IP transit directly from IDACORE at the North facility?
Yes. IDACORE runs its own ASN and BGP peering, and IP transit is available at IDACORE North on the same pricing as all other sites — 100M at $170/month up to 100G at $11,050/month, billed on committed bandwidth at the 95th percentile with no per-GB egress surprises.
If your DR plan currently depends on a facility whose exact address you can't state in an audit, it's time to fix that. Talk to IDACORE about colocating your DR site in Coeur d'Alene and get a facility address, a compliance certification list, and a $300/kW/month rate you can put directly into your next audit response.
