Deployment Assessment
Inventory the client version, custom modifications, validator setup and application dependencies of the existing network.
Polygon Edge Review & Migration
Preserve Your Existing Network. Plan Its Next Chapter.
Polygon Edge network assessment and migration planning for existing deployments, application compatibility, data continuity and a tested transition.
- Existing-network inventory
- Compatibility assessment
- Data continuity planning
- Cutover rehearsals
What we build
Discuss Your ProjectPolygon Edge Review & Migration Services
Target Architecture Review
Compare maintained alternatives against execution, access-control and operational requirements before choosing a target.
Application Migration
Review contracts, RPC behaviour, wallets and indexing integrations to identify changes required by the selected destination.
Transition Rehearsal
Test state and history requirements, application acceptance and rollback boundaries before scheduling a production cutover.
From scope to launch
Start Your ProjectOur Development Process
- 01
Discovery
Record the current deployment, dependencies and operational constraints.
- 02
Architecture
Compare migration candidates and document compatibility gaps.
- 03
Implementation
Build a rehearsal environment for applications and required data.
- 04
Verification
Validate historical access, cutover steps and recovery boundaries.
- 05
Launch & Support
Execute an approved transition with monitoring and operator handover.
Start with the network you already operate
Polygon Edge's upstream repository is archived. For an existing deployment, we begin with the running version, custom changes and application dependencies, then compare maintenance and migration options. A transition is planned around data continuity and a rehearsed cutover, not an assumed drop-in replacement.
Maintain temporarily or migrate?
Make the tradeoff explicit: an archived upstream increases maintenance responsibility, while migration has its own compatibility risks.
What must remain accessible?
Define how users will access historic records and which application state must be preserved through the transition.
Practical Use Cases
01
Existing Edge deployments
Create a documented assessment of a running network before committing to changes.
02
Application continuity
Keep contract integrations and user transaction journeys central to the migration plan.
03
Platform replacement planning
Evaluate a maintained stack using representative workloads and a clear acceptance checklist.
Selected for your scope
Technology & Delivery Toolkit
We choose the implementation tools after confirming the architecture and integrations.
- Deployment inventory
- Compatibility test suite
- State and history validation
- Cutover runbooks
Polygon Edge Review & Migration FAQs
Is Polygon Edge actively maintained upstream?
The official Polygon Edge repository is archived and read-only. We treat this page as support for assessment and transition planning, not a recommendation to begin a new production network on an archived default.
Can we migrate without changing anything?
That cannot be assumed. Contract behaviour, state handling, RPC interfaces and infrastructure must be assessed against the target architecture before a migration plan is approved.
Plan your Edge transition around business continuity
Tell us what you want to build. We’ll help define the next practical step.