Transparent state
Active, archived, expired, pending, and Trash states describe what the public route will do.
Platform comparison
The right link platform depends on workflow, not a feature-count headline. Gods.ly focuses on readable routes, server-enforced workspace ownership, separate analytics ingestion, and recoverable lifecycle states.
Review Gods.ly pricingActive, archived, expired, pending, and Trash states describe what the public route will do.
Server checks and database rules keep each workspace’s records separate.
OpenAPI and generated clients make automation behavior reviewable.
Evaluate how each platform handles short-name conflicts, connection retries, destination changes, team removal, custom-domain verification, exports, and link deletion. These details matter after the first link is created.
Gods.ly uses request and version checks so retried or simultaneous edits do not create duplicates or silently overwrite newer work.
Inventory every active alias, domain, destination, expiration, password rule, and historical redirect before switching traffic. A migration should produce a source-to-target mapping and a zero-unexplained-mismatch report.
Do not change DNS until top routes and rollback behavior have been rehearsed.
Gods.ly pricing shows the current published packages, currencies, and included limits. Confirm the current published limits and prices on the pricing page before making a plan decision.
Check the latest official catalogue for each service you are considering, since pricing and package limits can change.
Common questions
Yes, when they do not conflict with reserved platform routes and their source destination and lifecycle are reconciled.
No. Competitor pricing changes; evaluate their current official catalog and compare it with the live Gods.ly pricing page.
Start with a real workflow