Your own chain, or the nodes under someone else's.
Chain infrastructure is either a network of your own or the nodes that keep you on someone else's. neoStack™ builds application-specific chains and L2 rollups where a shared network will not do, and runs validator and RPC operations to the same uptime commitment as the gaming platform. Everything is infrastructure as code in your repository.
Validator fleet · neofund-subnet
block 4,218,9041.2s
finality
4/5
signing
ready
handover
99.99%
Node uptime, 24-month rolling
3+
Regions per fleet, minimum
15 min
P1 response, 24/7
Day one
Handover documentation
Four questions before anyone builds a chain
Most projects that want their own chain should use one that already exists. The four questions below decide it.
Question 1
Do your counterparties already use a chain?
If the people you need to transact with are on Ethereum, you are probably on Ethereum. Liquidity and existing integrations beat every benchmark.
Question 2
Is blockspace contention actually hurting you?
Own blockspace is the strongest argument for a rollup or an app-chain, and it only applies if you are being priced out or delayed at peak. Measure it before you build for it.
Question 3
Does a regulator require a closed validator set?
This is the argument that most often holds. Institutional issuance frequently requires that validators be known and contractually bound, which a public chain cannot offer. If this is your constraint, a permissioned network is the answer.
Question 4
Can you carry the security budget?
Your own chain means your own consensus, your own validator recruitment, and your own economic security. That is a permanent operating commitment, and it stops most app-chain plans.
Four architectures, and what each costs you
Every row has a trade-off in the third column. More control is more liability, and the right answer is usually the least of it that meets your constraint.
| Architecture | Typical stacks | What you gain | What you take on |
|---|---|---|---|
| Shared L1 / L2 | Ethereum, Base, Arbitrum, Polygon | Liquidity and integrations already there | You compete for blockspace and inherit the chain's governance |
| L2 rollup | OP Stack, Arbitrum Orbit, zkSync | Own blockspace, settles to Ethereum | Sequencer to run; bridge risk to design around carefully |
| App-chain / subnet | Avalanche subnet, Cosmos SDK, Polkadot | Full control of fees, governance and validator set | You own consensus, security budget and validator recruitment |
| Permissioned network | Hyperledger Besu, Quorum | Closed validator set, no public exposure | The usual institutional answer |
Running the fleet
Node operations is either done properly or discovered to have been done badly during an incident. These four things separate the two.
Multi-region by default
Validators and RPC endpoints across at least three regions, with automatic failover tested on a schedule.
Validator key custody
Signing keys held in HSM-backed infrastructure with the same custody standards as neoVault™, because a compromised validator key is a compromised chain.
Monitoring & alerting
Liveness, block production, peer count, sync lag, and fork detection watched continuously, with paging into your own on-call rotation as well as ours.
Reproducible deployment
Infrastructure as code, pinned client versions, and documented upgrade procedures, so the fleet can be rebuilt from a repository.
Built so you can leave
Everything needed to run this without us exists from the first deployment, and we rehearse the handover on request.
Delivered from day one
Governance stays yours
On a contentious fork we present the technical position and the implications. Which side you follow is a governance decision and we do not make it on your behalf.
No proprietary layer
Standard clients, standard tooling, no aineobit-specific component that only we can operate. The stack you run is the stack the wider ecosystem runs.
99.99%
node uptime, 24-month rolling
3+
regions per fleet, minimum
15 min
P1 response, 24/7
Day one
handover documentation
What infrastructure teams ask
Probably not. The test is four questions: are your counterparties already somewhere, is blockspace contention measurably hurting you, does a regulator require a closed validator set, and can you fund consensus security permanently. Most projects fail the first question, and a shared network serves them better.
Find out if you need your own chain
A technical session with the engineers who operate these: the four questions applied to your case, what the architecture would cost to run annually, and a clear answer on whether a shared network serves you better.