PHPackages                             kolossal-io/laravel-multiplex - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Database & ORM](/categories/database)
4. /
5. kolossal-io/laravel-multiplex

ActiveLibrary[Database & ORM](/categories/database)

kolossal-io/laravel-multiplex
=============================

A Laravel package to attach versioned meta data to Eloquent models.

v3.0.0(2w ago)292110.7k↓58.1%101MITPHPPHP ^8.2CI passing

Since Oct 20Pushed 5d ago3 watchersCompare

[ Source](https://github.com/kolossal-io/laravel-multiplex)[ Packagist](https://packagist.org/packages/kolossal-io/laravel-multiplex)[ Docs](https://github.com/Kolossal-io/laravel-multiplex)[ RSS](/packages/kolossal-io-laravel-multiplex/feed)WikiDiscussions main Synced 4d ago

READMEChangelog (10)Dependencies (36)Versions (62)Used By (1)

 [    ![Multiplex](https://raw.githubusercontent.com/kolossal-io/laravel-multiplex/HEAD/.github/logo-light.svg)  ](https://github.com/kolossal-io/laravel-multiplex)

 A Laravel package to attach time-sliced meta data to Eloquent models.

 [![Laravel](https://camo.githubusercontent.com/461126f08d27f3d345ebd278bffda768e6a4bb187631dc6b2f006cff83d45f1c/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f4c61726176656c2d31312e302b2d677265656e2e7376673f7374796c653d666c61742d737175617265)](https://packagist.org/packages/kolossal-io/laravel-multiplex) [![Latest Version on Packagist](https://camo.githubusercontent.com/e8836693690dbb64422b8fedd9e2e5497e3fd28bb1f1406c7fc4d2a46e82be40/68747470733a2f2f696d672e736869656c64732e696f2f7061636b61676973742f762f6b6f6c6f7373616c2d696f2f6c61726176656c2d6d756c7469706c65782e7376673f7374796c653d666c61742d737175617265)](https://packagist.org/packages/kolossal-io/laravel-multiplex) [ ![](https://camo.githubusercontent.com/1d5296302a6bb7028d65bb642a7a93fabb7b71210bd0960548d0ae7ba2638e45/68747470733a2f2f636f6465636f762e696f2f67682f6b6f6c6f7373616c2d696f2f6c61726176656c2d6d756c7469706c65782f6272616e63682f6d61696e2f67726170682f62616467652e7376673f746f6b656e3d33333033353447493330) ](https://codecov.io/gh/kolossal-io/laravel-multiplex) [![GitHub Tests Action Status](https://github.com/kolossal-io/laravel-multiplex/actions/workflows/tests.yml/badge.svg)](https://github.com/kolossal-io/laravel-multiplex/actions/workflows/tests.yml)

 [View Table of Contents](#table-of-contents)

---

What it does
------------

[](#what-it-does)

Multiplex allows you to attach time-sliced metadata to Eloquent models in a convenient way.

```
$post = \App\Models\Post::first();

// Set meta fluently for any key – `likes` is no column of `Post`.
$post->likes = 24;

// Or use the `setMeta` method.
$post->setMeta('likes', 24);

// You may also schedule changes, for example change the meta in 2 years:
$post->setMetaAt('likes', 6000, '+2 years');
```

Features
--------

[](#features)

- Metadata is saved in versions: Schedule changes to metadata, change history or retrieve metadata for a specific point in time.
- Supports fluent syntax: Use your model’s metadata as if they were properties.
- Polymorphic relationship allows adding metadata to any Eloquent model without worrying about the database schema.
- Easy to try: Extend existing database columns of your model with versionable metadata without touching or deleting your original columns.
- Type conversion system heavily based on [Laravel-Metable](https://github.com/plank/laravel-metable) allows data of numerous different scalar and object types to be stored and retrieved.

Why another Metadata Package?
-----------------------------

[](#why-another-metadata-package)

The main difference is that the metadata in Multiplex has a timestamp that defines validity. This allows changes to be tracked and planned. You can inspect all metadata on your model at a specific point in time and Multiplex will by default only give you the most current.

Since Multiplex is storing the metadata in a [polymorphic](https://laravel.com/docs/9.x/eloquent-relationships#polymorphic-relationships) table, it can easily be plugged into existing projects to expand properties of your models. This even works without removing the relevant table columns of your model: They are used as a fallback.

And it’s low profile: If you don't like it, just [remove the `HasMeta` Trait](#installation) and everything is back to normal.

Table of Contents
-----------------

[](#table-of-contents)

- [Requirements](#requirements)
- [Installation](#installation)
- [Attaching Metadata](#attaching-metadata)
- [Retrieving Metadata](#retrieving-metadata)
- [Query by Metadata](#query-by-metadata)
- [Events](#events)
- [Time Traveling](#time-traveling)
- [Limit Meta Keys](#limit-meta-keys)
- [Extending Database Columns](#extending-database-columns)
- [Deleting Metadata](#deleting-metadata)
- [Performance](#performance)
- [Configuration](#configuration)
- [Enum Support](#enum-support)
- [UUID and ULID Support](#uuid-and-ulid-support)

Requirements
------------

[](#requirements)

Since Version 2 **Multiplex** uses **SQL Window Functions** (such as `ROW_NUMBER() OVER (...)`) for efficient and scalable queries on meta data (e.g., to determine the latest or current meta per key). This enables much better performance for large datasets compared to classic subqueries or group-by/aggregate approaches. Your database must support SQL Window Functions. This has been tested on:

- MySQL **8.0+**
- PostgreSQL **12.0+**
- SQLite **3.25+**

Installation
------------

[](#installation)

You can install the package via composer:

```
composer require kolossal-io/laravel-multiplex
```

Publish the migrations to create the `meta` table where metadata will be stored.

```
php artisan migrate
```

Attach the `HasMeta` trait to any Eloquent model that needs meta attached.

```
use Illuminate\Database\Eloquent\Model;
use Kolossal\Multiplex\HasMeta;

class Post extends Model
{
    use HasMeta;
}
```

Attaching Metadata
------------------

[](#attaching-metadata)

By default you can use any `key` for attaching metadata. You can [limit which keys can be used](#limit-meta-keys).

```
$model->setMeta('foo', 'bar');
// or
$model->foo = 'bar';
```

You may also set multiple meta values by passing an `array`.

```
$model->setMeta([
    'hide' => true,
    'color' => '#000',
    'likes' => 24,
]);
```

All metadata will be stored automatically when saving your model.

```
$model->foo = 'bar';

$model->isMetaDirty(); // true

$model->save();

$model->isMetaDirty(); // false
```

You can also save your model without saving metadata.

```
$model->saveWithoutMeta();

$model->isMetaDirty(); // true

$model->saveMeta();
```

You can reset metadata changes that were not yet saved.

```
$model->resetMeta();
```

Metadata can be stored right away without waiting for the parent model to be saved.

```
// Save the given meta value right now.
$model->saveMeta('foo', 123.45);

// Save only specific keys of the changed meta.
$model->setMeta(['color' => '#fff', 'hide' => false]);
$model->saveMeta('color');
$model->isMetaDirty('hide'); // true

// Save multiple meta values at once.
$model->saveMeta([
    'color' => '#fff',
    'hide' => true,
]);
```

### Schedule Metadata

[](#schedule-metadata)

You can save metadata for a specific publishing date.

```
$user = Auth::user();

$user->saveMeta('favorite_band', 'The Mars Volta');
$user->saveMetaAt('favorite_band', 'Portishead', '+1 week');

// Changing taste in music: This will return `The Mars Volta` now but `Portishead` in a week.
$user->favorite_band;
```

This way you can change historic data as well.

```
$user->saveMetaAt('favorite_band', 'Arctic Monkeys', '-5 years');
$user->saveMetaAt('favorite_band', 'Tool', '-1 year');

// This will return `Tool` – which is true since this is indeed a good band.
$user->favorite_band;
```

You may also save multiple metadata records at once.

```
$user->setMeta('favorite_color', 'blue');
$user->setMeta('favorite_band', 'Jane’s Addiction');
$user->saveMetaAt('+1 week');

// or

$user->saveMetaAt([
    'favorite_color' => 'blue',
    'favorite_band' => 'Jane’s Addiction',
], '+1 week');
```

### How Metadata is stored

[](#how-metadata-is-stored)

Multiplex will store metadata in a polymorphic table and take care of serializing and unserializing datatypes for you. The underlying polymorphic `meta` table may look something like this:

metable\_typemetable\_idkeyvaluetypepublished\_atApp\\Models\\Post`1`color\#000string2022-11-29 13:13:45App\\Models\\Post`1`likes24integer2020-01-01 00:00:00App\\Models\\Post`1`hidetrueboolean2022-11-27 16:32:08App\\Models\\Post`1`color\#fffstring2030-01-01 00:00:00The corresponding meta values would look like this:

```
$post = Post::find(1);

$post->color; // string(4) "#000"
$post->likes; // int(24)
$post->hide; // bool(true)

// In the year 2030 `$post->color` will be `#fff`.
```

Retrieving Metadata
-------------------

[](#retrieving-metadata)

You can access metadata as if they were properties on your model.

```
$post->likes; // (int) 24
$post->color; // (string) '#000'
```

Or use the `getMeta()` method to specify a fallback value for non-existent meta.

```
$post->getMeta('likes', 0); // Use `0` as a fallback.
```

You can also retrieve the `meta` relation on your model. This will only retrieve the most recent value per `key` that is released yet.

```
$post->saveMeta([
    'author' => 'Anthony Kiedis',
    'color' => 'black',
]);

$post->saveMetaAt('author', 'Jimi Hendrix', '1970-01-01');
$post->saveMetaAt('author', 'Omar Rodriguez', '+1 year');

$post->meta->pluck('value', 'key');

/**
 * Illuminate\Support\Collection {
 *   all: [
 *     "author" => "Anthony Kiedis",
 *     "color" => "black",
 *   ],
 * }
 */
```

There is a shorthand to pluck all the current meta data attached to the model. This will include all [explicitly defined meta keys](#limit-meta-keys) with a default of `null`.

```
// Allow any meta key and explicitly allow `foo` and `bar`.
$post->metaKeys(['*', 'foo', 'bar']);

$post->saveMeta('foo', 'a value');
$post->saveMeta('another', true);

$post->pluckMeta();
/**
 * Illuminate\Support\Collection {
 *   all: [
 *     "foo" => "a value",
 *     "bar" => null,
 *     "another" => true,
 *   ],
 * }
 */
```

If you instead want to retrieve all meta that was published yet, so also include historic meta, use the `publishedMeta` relation.

```
// This array will also include `Jimi Hendrix´.
$post->publishedMeta->toArray();
```

If you want to inspect *all* metadata including unpublished records, use the `allMeta` relation.

```
$post->allMeta->toArray();
```

If you want to inspect *historic* metadata including only records that are not valid anymore, use the `historicMeta` relation.

```
$post->historicMeta->toArray();
```

There is also a `plannedMeta` relation that can be used to inspect meta not yet published.

```
$post->plannedMeta->toArray();
```

You can determine if a `Meta` instance is the most recent published record for the related model or if it is not yet released.

```
$meta = $post->allMeta->first();

$meta->is_current; // (bool)
$meta->is_planned; // (bool)
```

Please note that the `is_current` attribute is quite heavy, since it will first have to load the most recent meta of the corresponding model to check against.

### Querying `Meta` Model

[](#querying-meta-model)

There are also some query scopes on the `Meta` model itself that may be helpful.

```
Meta::published()->get(); // Only current and historic meta.

Meta::planned()->get(); // Only meta not yet published.

Meta::publishedBefore('+1 week')->get(); // Only meta published by next week.

Meta::publishedAfter('+1 week')->get(); // Only meta still unpublished in a week.

Meta::current()->get(); // Only current meta without planned or historic data.

Meta::history()->get(); // Only historic meta that is not valid anymore.
```

By default these functions will use `Carbon::now()` to determine what metadata is considered the most recent, but you can also pass a datetime to look from.

```
// Get records that have been current a month ago.
Meta::current('-1 month')->get();
```

The `current` and `history` scopes are not available on any of the `meta` relations. Use the `meta` and `historicMeta` relations instead.

```
// This will NOT work.
$model->allMeta()->current()->get();
$model->allMeta()->history()->get();

// Use the specific relations instead.
$model->meta()->get();
$model->historicMeta()->get();
```

Query by Metadata
-----------------

[](#query-by-metadata)

### Querying Metadata Existence

[](#querying-metadata-existence)

You can query records having meta data for the given key(s).

```
// Find posts having at least one meta records for `color` key.
Post::whereHasMeta('color')->get();

// Or pass an array to find records having meta for at least one of the given keys.
Post::whereHasMeta(['color', 'background_color'])->get();
```

### Querying Metadata Absence

[](#querying-metadata-absence)

You can query records not having meta data for the given key(s).

```
// Find posts not having any meta records for `color` key.
Post::whereDoesntHaveMeta('color')->get();

// Or find records not having meta for any of the given keys.
Post::whereDoesntHaveMeta(['color', 'background_color'])->get();
```

### Querying Metadata by Value

[](#querying-metadata-by-value)

You can retrieve models having meta with the given key and value.

```
// Find posts where the current attached color is `black`.
Post::whereMeta('color', 'black')->get();

// Find posts where the current attached color is not `black`.
Post::whereMeta('color', '!=', 'black')->get();

// Find posts that are `visible`.
Post::whereMeta('visible', true)->get();

// There are alternatives for building `or` clauses for all scopes.
Post::whereMeta('visible', true)->orWhere('hidden', false)->get();
```

Multiplex will take care of finding the right datatype for the passed query.

```
// Matches only meta records with type `boolean`.
Post::whereMeta('hidden', false)->get();

// Matches only meta records with type `datetime`.
Post::whereMeta('release_at', '', '100')->get();
```

You can also define which [datatype](config/multiplex.php) to use.

```
Post::whereMetaOfType('integer', 'count', '0')->get();

Post::whereMetaOfType('null', 'foo', '')->get();
```

### Querying empty or non-empty Metadata

[](#querying-empty-or-non-empty-metadata)

You can query for empty or non-empty metadata where `null` or empty strings would be considered being empty.

```
Post::whereMetaEmpty('favorite_band')->get();

// Get all posts having meta names `likes` and `comments` where *both* of them are not empty.
Post::whereMetaNotEmpty(['likes', 'comments'])->get();
```

Events
------

[](#events)

You can listen for the following events that will be fired by Multiplex.

### `MetaHasBeenAdded`

[](#metahasbeenadded)

This event will be fired once a new version of meta is saved to the model.

```
use Kolossal\Multiplex\Events\MetaHasBeenAdded;

class SomeListener
{
    public function handle(MetaHasBeenAdded $event)
    {
        $event->meta; // The Meta model that was added.
        $event->model; // The parent model, same as $event->meta->metable.
        $event->type; // The class name of the parent model.
    }
}
```

### `MetaHasBeenRemoved`

[](#metahasbeenremoved)

This event will be fired once metadata is removed by using [`deleteMeta`](#deleting-metadata). The event will fire only once per key and the `$meta` property on the event will contain the latest meta only.

```
use Kolossal\Multiplex\Events\MetaHasBeenRemoved;

class SomeListener
{
    public function handle(MetaHasBeenRemoved $event)
    {
        $event->meta; // The Meta model that was removed.
        $event->model; // The parent model, same as $event->meta->metable.
        $event->type; // The class name of the parent model.
    }
}
```

Time Traveling
--------------

[](#time-traveling)

You can get the metadata for a model at a specific point in time.

```
$user = Auth::user()->withMetaAt('-1 week');
$user->favorite_band; // Tool
$user->withMetaAt(Carbon::now())->favorite_band; // The Mars Volta
```

This way you can inspect the whole set of metadata that was valid at the time.

```
Post::first()->withMetaAt('2022-10-01 15:00:00')->meta->pluck('value', 'key');
```

You can also query by meta for a specific point in time.

```
Post::travelTo(Carbon::now()->subWeeks(2))->whereMetaIn('foo', [false, 0])->get();

Post::travelTo(Carbon::now()->addYears(2))->where('category', 'tech')->get();
```

Remember to travel back if you want to perform further actions.

```
Post::travelTo(Carbon::now()->subYear())->where('category', 'tech')->get();
Post::where('category', 'tech')->get(); // Will still look for meta published last year.

Post::travelBack();
Post::where('category', 'tech')->get(); // Find current meta.
```

Limit Meta Keys
---------------

[](#limit-meta-keys)

You can limit which keys can be used for metadata by setting `$metaKeys` on the model.

```
class Post extends Model
{
    use HasMeta;

    protected array $metaKeys = [
        'color',
        'hide',
    ];
}
```

By default all keys are allowed.

```
protected array $metaKeys = ['*'];
```

You can also change the allowed meta keys dynamically.

```
$model->metaKeys(['color', 'hide']);
```

You might as well cast your attributes using the `MetaAttribute` cast which will automatically allow the attribute being used as a meta key.

```
use Kolossal\Multiplex\MetaAttribute;

class Post extends Model
{
    use HasMeta;

    protected $metaKeys = [];

    protected $casts = [
        'body' => MetaAttribute::class,
    ];
}
```

Trying to assign a value to a meta key that is not allowed will throw a `Kolossal\Multiplex\Exceptions\MetaException`.

If you have [Eloquent Strictness](https://laravel.com/docs/10.x/eloquent#configuring-eloquent-strictness) enabled it is recommended to [explicitely cast the meta attributes to `MetaAttribute`](https://github.com/kolossal-io/laravel-multiplex/issues/19#issuecomment-1584150675).

Typecast Meta Keys
------------------

[](#typecast-meta-keys)

Sometimes you may wish to force typecasting of meta attributes. You can bypass guessing the correct type and define which type should be used for specific meta keys.

```
protected array $metaKeys = [
    'foo',
    'count' => 'integer',
    'color' => 'string',
    'hide' => 'boolean',
];
```

Extending Database Columns
--------------------------

[](#extending-database-columns)

By default Multiplex will not touch columns of your model. But sometimes it might be useful to have meta records as an extension for your existing table columns.

Consider having an existing `Post` model with only a `title` and a `body` column. By explicitely adding `body` to our array of meta keys `body` will be handled by Multiplex from now on – not touching the `posts` table, but using the database column as a fallback.

```
class Post extends Model
{
    use HasMeta;

    protected $metaKeys = [
        '*',
        'body',
    ];
}
```

```
\DB::table('posts')->create(['title' => 'A title', 'body' => 'A body.']);

$post = Post::first();

$post->body; // A body.

$post->body = 'This. Is. Meta.';
$post->save();

$post->body; // This. Is. Meta.
$post->deleteMeta('body');

$post->body; // A body.
```

In case of using Multiplex for extending table columns, Multiplex will remove the original column when retrieving models from the database so you don’t get stale data.

Deleting Metadata
-----------------

[](#deleting-metadata)

You can delete any metadata associated with the model from the database.

```
// Delete all meta records for the `color` key.
$post->deleteMeta('color');

// Or delete all meta records associated with the model.
$post->purgeMeta();
```

Performance
-----------

[](#performance)

Since Multiplex stores metadata in a polymorphic [One To Many](https://laravel.com/docs/9.x/eloquent-relationships#one-to-many-polymorphic-relations) relationship querying your models could easily result in a [`N+1` query problem](https://laravel.com/docs/9.x/eloquent-relationships#eager-loading).

Depending on your use case you should consider eager loading the `meta` relation, for example using `$with` on your model. This might be especially useful if you are [extending database columns](#extending-database-columns).

```
// Worst case: 26 queries if `color` is a meta value.
$colors = Post::take(25)->get()->map(
    fn ($post) => $post->color;
);

// Same result with only 2 queries.
$colors = Post::with('meta')->take(25)->get()->map(
    fn ($post) => $post->color;
);
```

Configuration
-------------

[](#configuration)

There is no need to configure anything but if you like, you can publish the config file with:

```
php artisan vendor:publish --tag="multiplex-config"
```

Enum Support
------------

[](#enum-support)

Multiplex supports [backed enumerations](https://www.php.net/manual/en/language.enumerations.backed.php) introduced in PHP 8.1 whereas basic enumerations would not work.

```
enum SampleEnum: string
{
    case Hearts = 'hearts';
    case Diamonds = 'diamonds';
}

$model->saveMeta('some_key', SampleEnum::Diamonds);

// true
$model->some_key === SampleEnum::Diamonds;
```

UUID and ULID Support
---------------------

[](#uuid-and-ulid-support)

If your application uses UUIDs or ULIDs for the model(s) using metadata, you may set the `multiplex.morph_type` setting to `uuid` or `ulid` **before** running the migrations. You might as well set the `MULTIPLEX_MORPH_TYPE` environment variable instead, if you don’t want to publish the configuration file.

This will ensure `Meta` models will use UUID/ULID and that proper keys and foreign keys are used when running the migrations.

Credits
-------

[](#credits)

This package is heavily based on and inspired by [Laravel-Metable](https://github.com/plank/laravel-metable) by [Sean Fraser](https://github.com/frasmage) as well as [laravel-meta](https://github.com/kodeine/laravel-meta) by [Kodeine](https://github.com/kodeine). The [Package Skeleton](https://github.com/spatie/package-skeleton-laravel) by the great [Spatie](https://spatie.be/) was used as a starting point.

License
-------

[](#license)

 [    ![Multiplex](https://raw.githubusercontent.com/kolossal-io/laravel-multiplex/HEAD/.github/kolossal-log-light.svg)  ](https://kolossal.io)

Copyright © [kolossal](https://kolossal.io). Released under [MIT License](LICENSE.md).

###  Health Score

65

—

FairBetter than 99% of packages

Maintenance98

Actively maintained with recent releases

Popularity50

Moderate usage in the ecosystem

Community21

Small or concentrated contributor base

Maturity73

Established project with proven stability

 Bus Factor1

Top contributor holds 79.8% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~26 days

Recently: every ~15 days

Total

52

Last Release

19d ago

Major Versions

v0.10.2 → v1.0.02023-08-16

1.x-dev → v2.0.02026-04-15

2.x-dev → 3.x-dev2026-04-19

v2.0.2 → v3.0.02026-06-16

PHP version history (3 changes)v0.1.0PHP ^8.1

v0.1.2PHP ^8.0

3.x-devPHP ^8.2

### Community

Maintainers

![](https://www.gravatar.com/avatar/ea9eff74314c8976d12d05224a33b46860e46a8955910b45f42370525aa15d8d?d=identicon)[kolossal.io](/maintainers/kolossal.io)

---

Top Contributors

[![marijoo](https://avatars.githubusercontent.com/u/360736?v=4)](https://github.com/marijoo "marijoo (265 commits)")[![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?v=4)](https://github.com/dependabot[bot] "dependabot[bot] (40 commits)")[![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?v=4)](https://github.com/github-actions[bot] "github-actions[bot] (22 commits)")[![semantic-release-bot](https://avatars.githubusercontent.com/u/32174276?v=4)](https://github.com/semantic-release-bot "semantic-release-bot (2 commits)")[![michaelnabil230](https://avatars.githubusercontent.com/u/46572405?v=4)](https://github.com/michaelnabil230 "michaelnabil230 (1 commits)")[![vinnygambiny](https://avatars.githubusercontent.com/u/16881513?v=4)](https://github.com/vinnygambiny "vinnygambiny (1 commits)")[![ysfkaya](https://avatars.githubusercontent.com/u/16710972?v=4)](https://github.com/ysfkaya "ysfkaya (1 commits)")

---

Tags

eloquentlaravelmetametadatatimetravellaraveleloquentmetadatametakolossallaravel-multiplex

###  Code Quality

TestsPest

Static AnalysisPHPStan

Code StyleLaravel Pint

### Embed Badge

![Health badge](/badges/kolossal-io-laravel-multiplex/health.svg)

```
[![Health](https://phpackages.com/badges/kolossal-io-laravel-multiplex/health.svg)](https://phpackages.com/packages/kolossal-io-laravel-multiplex)
```

###  Alternatives

[illuminate/database

The Illuminate Database package.

2.8k54.9M11.7k](/packages/illuminate-database)[watson/validating

Eloquent model validating trait.

9803.5M54](/packages/watson-validating)[kodeine/laravel-meta

Fluent Meta Data for Eloquent Models, as if it is a property on your model.

421817.6k9](/packages/kodeine-laravel-meta)[reedware/laravel-relation-joins

Adds the ability to join on a relationship by name.

2121.3M18](/packages/reedware-laravel-relation-joins)[wnx/laravel-backup-restore

A package to restore database backups made with spatie/laravel-backup.

213421.5k2](/packages/wnx-laravel-backup-restore)[lacodix/laravel-model-filter

A Laravel package to filter, search and sort models with ease while fetching from database.

17558.6k](/packages/lacodix-laravel-model-filter)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)