Indianapolis · FJI analysis · Development economics

Two Indianapolis Data Centers Face Different Financing Hurdles

Published November 14, 2026 · Sources reviewed November 14, 2026

Sabey won incentive approval. DC BLOX faces a tax-break setback. Their paths show what zoning alone leaves unresolved.

Two Indianapolis data-center projects have permission to pursue development, but their incentive decisions have taken different turns. Sabey secured tax-abatement approval in September. DC BLOX reached November with an unfavorable committee recommendation and a further council decision ahead. [S2] · [S4]

For investors, the contrast exposes a risk that a zoning milestone can conceal. Permission to use land does not settle a project’s taxes, secure a tenant or fund construction. Clearing one decision can leave another decision capable of changing the size, timing or economics of a campus.

The comparison is between two development-stage campuses in the same city, not an operating winner and a cancelled rival. Nor does it establish why officials treated the packages differently. The projects have different sites, proposed investments, community commitments and approval paths.

Two campuses, different remaining decisions

Indianapolis project comparison · November 14, 2026
ProjectDocumented positionWhat remains unresolved
Sabey · 6400 Kentucky Avenue, Decatur TownshipMDC incentive approval announced September 16; $4.3 billion projected investmentCompliance with investment and construction conditions; tenant delivery, operating capacity and realized spending
DC BLOX · 305 Fintail Drive, east sideLand-use approval reported; November 9 committee recommendation against proposed abatementsFurther council/MDC action, customer commitments and the resulting phase economics

The figures describe proposed development, not comparable capital already deployed. They are not evidence that either campus has delivered computing capacity. [S2] · [S4]

Sabey’s approval still comes with conditions

Sabey’s September 16 approval reduced uncertainty over an important component of its expected costs. Indy Economic Development said the company and its tenant were expected to invest $4.3 billion, with an estimated $53 million in taxes during the abatement period. Those projections remain distinct from receipts. [S2]

The real-property resolution in the city’s hearing record shows what an approval still requires. It allows termination of the designation if construction does not begin within one year, or if the project materially departs from its description. It also calls for compliance monitoring and permits reductions, rescission or repayment of deductions when benefits are not achieved. [S1]

That makes an incentive approval a conditional economic advantage, not a guarantee that the entire investment arrives. For an investor evaluating delivery, the useful follow-up is evidence of qualifying construction, investment and customer service. For a resident evaluating benefits, it is the payment schedule and enforceability of the commitments.

The documents also contain a discrepancy worth retaining. The hearing resolution specifies a 60% deduction of increased real-property taxes for each of ten years, matching WFYI’s account of the approved terms. The economic-development announcement describes 50%. This analysis uses the resolution’s 60% schedule, identifies the conflicting summary, and does not claim to have reviewed a fully executed agreement or subsequent amendment. [S1] · [S2] · [S3]

DC BLOX’s land-use approval did not settle its tax package

DC BLOX’s east-side development already had land-use approval when the council committee voted 11–2 on November 9 to recommend rejecting roughly $113 million in proposed tax breaks, WFYI reported. That recommendation was not a binding denial by the full council and did not itself cancel the project. [S4]

The distinction is reflected in the council’s own documents. Proposals 345 and 346 address personal- and real-property statements of benefits. They explain that a statement of benefits for property in an allocation area needs council approval. This fiscal decision is separate from permission to use the land. [S5]

Customer commitments add another uncertainty. WFYI reported company testimony that neither building had full tenant commitments, with a challenge to the land-use approval cited as a constraint. That is an attributed account of the position at the hearing; it does not establish that the entire market lacks demand. [S4]

DC BLOX’s own plan separates a roughly 70,000-square-foot first building from a roughly 250,000-square-foot second building. It describes the first phase as serving network communications and local processing, while the second phase’s applications remain undefined. Treating both as one assured AI-capacity addition would go beyond the operator’s description. [S6]

Community commitments are part of the economics

The development case is more substantial than a tax-break headline alone. Indy Economic Development describes at least $29.8 million of Sabey commitments for roads and an aquatic center. DC BLOX promotes $30 million of east-side commitments and says it has reduced its design’s footprint and power demand. [S2] · [S6]

Those statements explain what the city and developers argue the projects would contribute. They do not establish that payments have been received or resolve neighborhood concerns. Opposition did not prevent Sabey’s incentive approval; the presence of a community package did not prevent DC BLOX’s committee setback. The record cannot isolate a single cause for the different votes. [S3] · [S4] · [S7]

Investor lens: price the decisions that remain

Our analysis: a development pipeline should distinguish land-use permission, incentive approval, customer commitments, construction funding and customer-ready delivery. These are separate obligations with different counterparties. This two-project comparison illustrates their separation; it is not a statistical estimate of cancellation risk across Indianapolis or the wider industry.

For Sabey, the remaining tests include compliance with the approved investment conditions and evidence that tenants turn planned capacity into service. For DC BLOX, unresolved incentives sit alongside customer commitments and phase decisions. A financing assessment would test the effect of changed taxes on each phase and identify who supplies capital while approvals or leases remain unsettled.

Neither the reviewed public packages nor the announced investment totals establish project returns, debt-service coverage or a revenue contribution to a listed company. No buy-or-sell conclusion follows from these votes. The distinction is simpler: an approved development opportunity is not yet an operating cash flow.

Fjord Journal’s Meta Lebanon investigation examines a different Indiana project’s power and public-benefit timetable. Our QTS Phoenix 3 update follows a verified substation milestone while keeping data-hall delivery unresolved. Each record tests the next step rather than treating an announced campus as completed capacity.

The next dated decision

The DC BLOX presentation in the council packet anticipates further MDC steps on November 18, a full-council vote on December 7 and a final MDC hearing on December 16. These are proposed legislative dates, subject to change—not approvals or construction-start promises. The next record to check is the actual disposition of those proceedings, followed by any final agreements and customer commitments. [S5]

Sources and claim boundaries · eight documents
  1. [S1] Indianapolis MDC: Sabey real-property resolution 2026-A-044 · 2026-09-16

    Hearing resolution specifies 60% real-property deduction for ten years, one-year construction-start condition, compliance surveys and potential reduction, rescission or repayment. Attachment has blank adoption signatures; approval outcome is corroborated separately. This is not proof of expenditure, delivered capacity or a final executed MOA.

  2. [S2] Indy Economic Development: Sabey approval announcement · 2026-09-16

    Confirms MDC incentive approval and forecasts $4.3 billion investment, $53 million taxes and at least $29.8 million community commitments. Its 50% real-property description conflicts with the hearing resolution and WFYI’s 60%; do not silently harmonize. Benefits are commitments/projections, not receipts.

  3. [S3] WFYI / Zak Cassel: Sabey approval · 2026-09-16

    Reports real-property approval 6–1 at 60% for ten years; personal-property approval 5–2 at 90% for fifteen years; estimated tax savings above $240 million. This is reported approval, not proof of operation or capital spent.

  4. [S4] WFYI / Eric Weddle: DC BLOX committee recommendation · 2026-11-09

    Reports 11–2 nonbinding recommendation to reject approximately $113 million in abatements, existing land-use approval, and company testimony that full tenant commitments had not been secured. Court challenge is reported, not adjudicated here.

  5. [S5] Indianapolis council packet: proposals 345 and 346 and DC BLOX presentation · 2026-11-02

    Personal/real-property benefits proposals require council action for an allocation area; blank passage fields do not establish adoption. Presentation anticipates November 18 MDC steps, December 7 council vote and December 16 final MDC hearing. Calendar is proposed, not an assured outcome.

  6. [S6] DC BLOX: Indianapolis Thunderbird project · Undated; checked November 14, 2026

    Operator proposes two phases, about 70,000 and 250,000 square feet; first-phase network/local processing and second-phase uses undefined; approximately $1.8–2 billion estimated investment; design reductions and $30 million community commitments. Website status text predates some later public decisions.

  7. [S7] Indy Economic Development: November 4 DC BLOX community meeting · 2026-11-04

    Identifies public presentation of anticipated benefits, proposed incentives and Inclusion Plan, zoning and good-neighbor commitments; supports the city/developer case, not delivered benefits.

  8. [S8] Indianapolis MDC September 16 meeting agenda · 2026-09-16

    Lists Sabey resolutions 2026-A-044 and 2026-A-045 and original attachments. Agenda alone does not establish the vote.

Public-source reporting and analysis as of November 14, 2026. No interviews, site visits, private leases, financing models or fully executed incentive agreements were reviewed. Government hearing documents, attributed developer statements and independent local reporting support this comparison. Neither project is presented as fully certified or operating; planned investments, tax savings and public benefits are not realized cash flows.

Following AI infrastructure? Bookmark Fjord Journal for sourced reporting on projects, power and capital.