Skip to main content

Understanding the Issues

Neutral explainers summarizing what is publicly known, why it matters, and what remains unresolved.

Each section below explains one part of the project: what is known, what public records indicate, and what has not yet been decided. Where reasonable people disagree, this page captures both views and flags uncertainty.

The Company, the NDA, and the MOU

What is known: The developer of record is Forgelight Ventures, LLC. Public reporting describes Forgelight as a holding company and references a Fortune 100 end user that has not been publicly identified in formal records.

Why anonymity is used: NDAs and holding-company entities are commonly used in economic development to protect competitive site-selection information.

Public concern: Residents have stated that without a confirmed end user, evaluating track record, commitments, and potential risks is difficult.

MOU context: A Memorandum of Understanding is generally non-binding and describes intent rather than final enforceable terms.

  • Not yet confirmed: End-user identity.
  • Not yet confirmed: Final binding terms and timing.
  • Not yet confirmed: Additional written commitments beyond the MOU.

Property Tax and Abatement

What is known: Arkansas programs may allow up to 65% property-tax abatement for up to 30 years when specific industrial financing structures and thresholds are met.

Qualification context: Program eligibility can vary by investment, payroll, and project category, including newer large-data-center pathways.

Source references: AEDC tier map and AEDC bond programs.

  • Question: Will this project seek an abatement, and of what size and duration?
  • Question: Which incentive program or combination applies?
  • Question: How would PILOT payments compare against a full tax bill?

Electricity

What is known: Public discussion indicates infrastructure coordination between Conway Corporation and Entergy Arkansas.

Rate context: Act 373 of 2025 changed how utilities can recover some costs during construction, while final rate changes still require regulatory approval. Source Act 373

  • Not yet known: Total project electricity demand.
  • Not yet known: Exact infrastructure scope and total cost.
  • Not yet known: Final cost allocation and any effect on existing customers.

Water

What is known: Public statements have referenced treated wastewater reuse as an expected cooling-water path, not a finalized binding commitment.

Volume caution: Public estimates for usage vary widely by cooling design and facility scale; estimate ranges should not be treated as a final project commitment.

  • Not yet known: Actual projected water demand.
  • Not yet known: Whether effluent reuse is finalized.
  • Not yet known: How water demand changes in later phases.

Environmental and Regulatory Review

Noise: Conway's ordinance sets day/night boundary limits and requires a noise study before project progression.

Enforcement: Ordinance penalties include fines, potential injunctive relief, and additional remedies for ongoing violations.

Additional agency review: Depending on final design and site details, reviews may involve federal and state agencies including aviation, waterway, and environmental regulators.

  • Not yet known: Whether independent environmental and economic studies will be completed.
  • Not yet known: Final required noise-study results.
  • Not yet known: Which agencies will issue final applicable approvals.

Jobs and Economic Impact

What is known: Public discussion distinguishes temporary construction employment from permanent operational roles.

Debate context: Supporters emphasize capital investment and long-term positions; skeptics question whether utility, water, and incentive commitments are proportional to projected permanent-job totals.

  • Not yet known: Final committed permanent job count and payroll terms.
  • Not yet known: Whether local hiring terms are explicitly required.
  • Not yet known: Net fiscal impact after infrastructure costs and incentives.