Bitrix Hermitage Laravel Package

Product Decisions This Supports

• Legacy modernization triage: Helps decide whether an existing 1C-Bitrix codebase should be maintained with Laravel-style conventions, wrapped behind an adapter, or scheduled for migration.
• Build vs. buy for internal tooling: Suitable only as a reuse candidate in inherited Bitrix systems; not a strategic buy for new products.
• Roadmap risk management: Since the package is archived, last released in 2018, and has minimal community traction, it should be treated as a legacy dependency rather than a foundation for new roadmap items.
• Use-case fit: Maintaining or extending older Bitrix applications where the team already understands the package; short-lived internal admin/back-office work; migration scaffolding or proof-of-concept work with a clear exit plan.
• Standardization decisions: Informs whether to preserve Bitrix-specific patterns or invest in a maintained Laravel-native stack for new development.

When to Consider This Package

• You have an existing Bitrix application with this dependency already in use, and the immediate goal is stabilization rather than modernization.
• The team needs Laravel-inspired structure or conventions inside a Bitrix context and accepts the maintenance, security, and compatibility risks of an archived package.
• The scope is short-lived, internal, or non-critical, with a documented plan to isolate, replace, or remove the package.
• You are evaluating a legacy migration path and need to understand how much behavior is coupled to the package before committing to a rewrite.

Look elsewhere when:

• You are building a new Laravel/PHP product or a customer-facing feature.
• You need long-term support, security patches, PHP 8+ compatibility, or active community maintenance.
• The package would sit on a critical path, handle payments, authentication, or other high-risk domains.
• A maintained Laravel-native solution, a newer Bitrix integration package, or a custom thin adapter would provide clearer ownership and lower lifecycle cost.

How to Pitch It (Stakeholders)

Executive summary: This is a low-traction, archived PHP package for legacy Bitrix-oriented development. It may help maintain an inherited system, but it is not a strategic platform investment. Approve it only as a contained legacy dependency with an explicit replacement or migration budget; do not build new roadmap commitments on it.

Engineering summary: Treat arrilot/bitrix-hermitage as frozen legacy code. If already present, pin the version, audit compatibility, isolate it behind an internal adapter, and add regression tests around its behavior. For new work, prefer maintained Laravel/Bitrix tooling or a custom integration layer with clear ownership. The 2018 last release, archived status, and 11 GitHub stars make it unsuitable as a long-term foundation.