Move from development to production - Neuro Developer Documentation

Treat production as a separate environment, not as a new hostname for the same setup. Recheck credentials, identities, providers, templates, privileges, federation, legal effect, and value.

Promotion checklist

Area	Confirm before promotion
Neuron	Production host, operator, supported version, enabled packages
Credentials	Production provisioning, storage, rotation, recovery, and revocation
Identity	Accepted providers, review policy, required assurance, and migration rules
Contracts	Approved production templates, parameters, parties, roles, and signing policy
Neuro-Features	Supported creation and transfer rules, state-machine definition, and event history
Payments	Supported product and provider, currency or value semantics, limits, approval, reconciliation
Federation	Trusted domains, remote participants, failure behavior, and permitted data sharing
Events	Durable delivery or polling, replay behavior, deduplication, and alerting
Operations	Logs without secrets, metrics, backups, incident owner, rollback or recovery

Promotion sequence

Repeatable development test
        ↓
Automated tests using repeatable data
        ↓
Staging settings and test data confirmed
        ↓
Success and failure paths tested end to end
        ↓
Production providers, templates, privileges, and federation approved
        ↓
Credential cutover and monitored production verification

Do not copy test identities, test signatures, development contracts, or test wallet assumptions into production unless the accountable operator explicitly documents a supported migration.

Get operator-specific requirements

Neuro does not currently provide one production checklist that applies to every operator and capability. Use this checklist with the operator of the production Neuron.

​Promotion checklist

​Promotion sequence

​Get operator-specific requirements

​Related guides

Promotion checklist

Promotion sequence

Get operator-specific requirements

Related guides