Weave Code
Neoeloquent Laravel Package
ulobby/neoeloquent
NeoEloquent brings Laravel's Eloquent ORM to Neo4j graph databases. Define graph-backed models, traverse relationships, and run Cypher queries using familiar Eloquent conventions, making it easier to integrate graph data into Laravel applications.
An extension of Laravel Elqouent that supports Neo4j, a native graph database
Frequently asked questions about Neoeloquent
- What is ulobby/neoeloquent and what does it do?
- NeoEloquent is a Composer package that extends Laravel's Eloquent ORM so models can be backed by Neo4j, a native graph database, instead of a relational store. You define graph-backed models, traverse relationships, and run Cypher queries using familiar Eloquent conventions. It is intended for applications where Neo4j is already a deliberate part of the architecture, such as recommendation engines, fraud detection, or knowledge graphs.
- How do I install NeoEloquent in a Laravel application?
- Install it with Composer using the package name ulobby/neoeloquent, then register the service provider and configure a Neo4j connection in your application's config. After that you can define graph-backed models and start querying. The package targets Laravel 12 and 13 on PHP 8.2 and above, so confirm your framework and PHP versions first.
- Which Laravel and PHP versions does NeoEloquent support?
- The current release line, ^9.9, supports Laravel 12 and 13 on PHP 8.2 through 8.5. For applications on Laravel 10 or 11, Composer resolves to the older 9.8.x line rather than failing, so there is no forced break. However, 9.8.x sits outside the maintained line and should be treated as a pinned, legacy dependency.
- Which Neo4j server versions are tested with NeoEloquent?
- The CI matrix exercises Neo4j 5.26, which is the version you should target for a supported deployment. Older Neo4j 5.x releases and 4.4 deployments are unverified, so behavior there is not guaranteed. Before relying on the package in production, confirm your Neo4j server patch level and run your own integration tests against it.
- How do I configure the Neo4j connection for NeoEloquent in Laravel?
- Add a Neo4j connection entry to your database configuration with the host, port, authentication credentials, and any required driver options, then point your graph models at that connection. The connection is used by the package's Eloquent-style query builder and relationship resolution. Operational readiness of the Neo4j cluster, including auth and backups, is a bigger factor in feasibility than the package itself.
- Can I use Eloquent relationships and Cypher queries with Neo4j models?
- Yes, NeoEloquent supports Eloquent-style relationship traversal and lets you run Cypher queries when you need direct graph access. Relationship direction and explicit relationship types still matter, so graph semantics shape your domain model rather than disappearing behind the ORM. Defining relationship types explicitly avoids ambiguity, especially for hasOne and belongsTo links.
- Does NeoEloquent support soft deletes and polymorphic relationships?
- The 9.9 release includes fixes around soft deletes and relationship inference, indicating these features are supported and actively worked on. If your models use SoftDeletes, onlyTrashed(), trashed counts, or polymorphic relationships, audit and test those paths explicitly during upgrade. The package's test suite coverage of these cases across both Laravel 12 and 13 is worth confirming with the maintainers.
- Is NeoEloquent a drop-in replacement for relational Eloquent models?
- No. NeoEloquent is a graph-database adapter, not a transparent substitute for a relational Eloquent model, and graph traversal, relationship direction, and Cypher semantics still influence how you model data. It works best for a bounded graph workload alongside existing relational Eloquent usage. Using Neo4j as your primary system of record requires real Cypher and graph-modeling expertise on the team.
- What happens if my application is still on Laravel 10 or 11?
- Nothing breaks immediately: Composer resolves to 9.8.x, so you can keep that version pinned and continue running. The catch is that 9.8.x no longer receives new fixes, and teams can silently drift outside the maintained line. Plan the framework upgrade to Laravel 12 or 13 as a separate change, then move the package to ^9.9 in the same window.
- Is NeoEloquent production-ready and actively maintained?
- The package is installable and usable in production where your stack matches the supported matrix, but it appears to be community-maintained with a small contributor base and a recent CI migration from Travis to GitHub Actions. Long-term support depth and the support policy for 9.8.x are unclear, so ask the maintainers about ownership, release cadence, and backward-compatibility posture. Pin versions per application and add a dependency-review check so teams do not drift onto an unsupported line.
Weaver
How can I help you explore Laravel packages today?