Fias Laravel Laravel Package

Product Decisions This Supports

• Russian-market address capture: powers address input, validation, and storage in checkout, onboarding, delivery, KYC, and CRM flows for any product serving Russian users. FIAS is the FNS's official address registry — using it gives canonical, government-aligned address data instead of free-text fields.
• Build vs. buy: a self-hosted, MIT-licensed alternative to paid address SaaS (DaData, Yandex Geocoder, Kontur). Relevant when per-lookup pricing, rate limits, or vendor lock-in make external API calls unattractive at scale.
• Data residency and compliance posture: address records and lookups stay inside our infrastructure, which simplifies the story on 152-ФЗ (personal data) and on-prem/offline deployment commitments.
• Air-gapped and offline deployments: enables enterprise, government-adjacent, and on-prem products where outbound calls to third-party address APIs are not permitted.
• Historical address handling: FIAS archives let us resolve or display addresses that no longer exist in the current registry — useful for order history, data migrations, and audit trails.
• Roadmap sequencing: a low-cost enabler to enter the RU market. It typically lands as table-stakes infrastructure (address quality) rather than a competitive differentiator.

Note: this package imports the registry — it is not a geocoder and does not provide fuzzy matching or typo correction. Position it accordingly.

When to Consider This Package

Consider adopting when:

• You're on Laravel/PHP and already committed to Eloquent and Artisan — this is a native bundle with migrations, models, and import commands.
• You need to store and query FIAS locally, not just validate against a live API.
• You're prepared to own the operations: downloading, importing, and refreshing the registry. The FIAS/GAR dumps are large (tens of GB of XML), so plan for disk, import time, and a refresh cadence.
• Your team can read Russian-language government documentation and the package source; there is no vendor SLA.
• You've done due diligence on maintenance: ~35 stars is a small community. Check open issues, commit cadence, PHP/Laravel version compatibility, and whether the package tracks GAR (the successor registry to FIAS since 2021).

Look elsewhere when:

• You need best-in-class fuzzy matching or suggestion UX — commercial APIs like DaData are materially better and cheaper to integrate.
• You need geocoding or coordinates — out of scope for this package.
• You're not on Laravel, or you don't want to own FIAS schema and import machinery — a managed data provider is lower total cost of ownership.
• Your footprint or latency budget cannot absorb a multi-gigabyte local address database.
• You need non-Russian addresses.
• You need vendor support, SLAs, or a large contributor base.

How to Pitch It (Stakeholders)

For executives: A free (MIT) package that lets us hold Russia's official address registry inside our own Laravel stack — no per-lookup API fees, no third-party dependency in the checkout path, and a cleaner data-residency story. It is infrastructure, not a headline feature: it unlocks RU-market flows and reduces ongoing vendor cost, at the price of some engineering ownership.

For engineering: Native Laravel integration — migrations, Eloquent models, and Artisan import commands for FIAS/GAR dumps. We own the schema, the import pipeline, and the refresh schedule; the package handles the mapping. Before committing, verify GAR-format support, measure import time and database size on a representative box, and confirm PHP/Laravel compatibility.

Risks to flag: the small community (~35 stars) means bus-factor and maintenance risk — plan a fallback (fork, or swap to a commercial provider) and a periodic review. Import volume is substantial. This is not a geocoder or de-duplicator; if product wants "type-ahead that fixes typos," budget for a hybrid approach (local FIAS storage plus an API for suggestions).

Recommended next step: a time-boxed spike — one service, one environment. Import a current dump, measure footprint and import time, wire a single address form, and benchmark against a DaData quote.