If your production systems run in Spokane and your compliance framework requires data to stay out of state lines you don't control, IDACORE North solves that at 45 minutes away in Coeur d'Alene, Idaho. It's open for orders now, billed at $300/kW/month, with no cross-border data transfer to worry about.
Why Does Spokane Need a DR Site Across the State Line?
Spokane is a strong regional market, but it's a Washington market — and a lot of companies there are discovering that "disaster recovery" and "regulatory compliance" aren't the same requirement. You can build redundancy within Washington and still fail a data residency clause if your auditor or your contract specifies data must stay within a particular state's jurisdiction, or simply must not commingle with a different regulatory regime.
That's the gap IDACORE North fills. Coeur d'Alene sits about 45 minutes from Spokane by I-90 — close enough for low-latency replication and fast recovery, far enough to be a genuinely separate facility, and squarely inside Idaho. For companies with Washington operations that need an Idaho-resident DR copy, or Idaho-headquartered companies that want a second Idaho site instead of routing data out of state, this is a straightforward answer.
We're not talking about a theoretical architecture here. IDACORE North is live, at 2115 N Government Way, taking orders today — not a roadmap item, not a pre-lease.
What Does "Data Residency" Actually Require?
A lot of vendors use "data residency" loosely. We mean it literally: your data does not cross state lines. Idaho and Eastern Oregon workloads stay in Idaho and Oregon. That matters for a specific set of buyers:
- Companies under state-level contractual requirements that specify data location (common in public sector and education contracts)
- Healthcare organizations that want a straightforward HIPAA story without explaining a multi-state replication path to an auditor
- Financial services firms with examiner requirements around data location and chain of custody
- Any company that's been burned by a hyperscaler region that technically spans multiple facilities across state or even national borders without clear disclosure
If your compliance officer has ever asked "where exactly does this data live" and you've had to go find out, Coeur d'Alene gives you an answer you can say out loud in one sentence.
How Does Per-U Colocation Work for a DR Deployment?
Disaster recovery doesn't need a full cabinet. Most DR deployments are a handful of servers running replication targets, backup appliances, or a cold/warm standby stack — not a production-scale footprint. IDACORE North rents space by the U, starting at a single rack unit, with no power commitment minimum.
Here's the part that trips people up: you're billed for the power your equipment draws, not for the space it occupies. There's no per-U rate and no per-cabinet flat fee. A single 200W DR server in 1U costs $60/month — 0.2 kW × $300/kW. Add a second appliance drawing 150W and your bill moves to $105/month. You're not paying for unused rack space you never touch, which is exactly backwards from how most colocation "starter" tiers work.
Example: A Spokane healthcare SaaS company needs a HIPAA-compliant DR target for 3 replication servers pulling a combined 600W. At IDACORE North that's 0.6 kW × $300 = $180/month, in a single rack unit, inside Idaho. No 36-month contract, no per-cabinet minimum, no out-of-state data path.
Spokane-to-Coeur d'Alene vs. Typical DR Alternatives
| Option | Distance from Spokane | Data stays in-state? | Contract term | Billing model |
|---|---|---|---|---|
| IDACORE North | ~45 min | Yes (Idaho) | 12 months | Power draw, $300/kW/month |
| Seattle-area DR facility | ~280 miles | No | Typically 36 months | Often per-cabinet/per-U flat fee |
| Hyperscaler multi-region | Varies, often undisclosed | Not guaranteed | Usage-based, variable | Egress-based, unpredictable |
The 12-month term matters more than it looks. Enterprise colocation providers typically lock you into 36-month agreements before you've proven out the DR architecture works for your workload. IDACORE North lets you validate the setup on a standard 12-month term instead of betting three years on day one.
What Does Regional Redundancy Actually Buy You?
Geographic separation only helps if the separation covers the risks that actually threaten your primary site. Coeur d'Alene is inland, away from Pacific Coast seismic and wildfire risk zones that affect much of the western US data center market. If your primary workload sits in Spokane, or anywhere on the I-90 corridor, you get a DR site that isn't exposed to the same regional weather or seismic event as your production environment, without the latency penalty of putting your failover somewhere on the other side of the country.
IDACORE North also connects to the same transit backbone as IDACORE Boise — same carriers, same on-net IP transit pricing. If your DR plan includes standing up application traffic during a failover event, not just replicating storage, you're not negotiating a separate network contract to do it. Transit is priced by committed bandwidth at 95th percentile billing: 1G runs $600/month, 10G runs $2,000/month — flat and predictable, not a surprise bill after a failover event spikes your usage.
A Note on Who Runs This
We've been doing network infrastructure in the Pacific Northwest for 30 years, including running our own ISP with our own ASN and BGP peering at the Seattle Internet Exchange. When we say "IP transit," we mean routes we announce and peer ourselves — not a resold circuit with someone else's support queue behind it. That matters during a DR event, when you need someone who can answer a routing question in minutes, not open a ticket and wait.
Frequently Asked Questions
Is IDACORE North a good fit for disaster recovery if my primary site is in Spokane?
Yes. Coeur d'Alene is about 45 minutes from Spokane, close enough for low-latency replication and fast recovery, while being a physically separate facility in a different state. For companies needing their DR data to stay specifically within Idaho for compliance reasons, this is the structural advantage — your production system can be in Washington while your DR copy stays in Idaho.
Does IDACORE North cost more than IDACORE Boise?
No. Power is billed at the same rate, $300/kW/month, at both facilities. IP transit pricing is also identical across IDACORE Boise and IDACORE North. Only IDACORE East, the Eastern Oregon AI/HPC facility, uses a different pricing structure.
Can I rent less than a full rack for a DR deployment at IDACORE North?
Yes. IDACORE North offers per-U colocation starting at a single rack unit, with no minimum power commitment. You're billed for the power your equipment draws, not a flat fee for the space — a 200W server costs $60/month (0.2 kW × $300/kW).
What compliance certifications apply to Idaho facilities?
IDACORE's certifications, including SOC 2 Type II, PCI DSS, NIST 800-53, SSAE-16, and HITRUST CSF, apply across the Idaho facilities, making both Boise and Coeur d'Alene suitable for HIPAA, financial services, and government compliance workloads that require audited infrastructure.
What contract length does IDACORE North require?
IDACORE North uses standard 12-month terms, compared to the 36-month terms common among enterprise colocation providers. This lets you validate a DR architecture on a shorter commitment before signing a longer agreement.
If Spokane compliance requirements or seismic risk exposure have you rethinking your DR architecture, IDACORE North's 45-minute proximity and strict Idaho data residency make it worth a direct conversation — reach out to our team to scope your deployment and get exact pricing for your power draw.
