Database schema

Every connection is one row in a single polymorphic table — connections by default, renamed via the table key. The published migration, abridged:

Schema::create('connections', function (Blueprint $table) use ($keyType): void {
    $table->id();
    $table->morphKey('connector', $keyType, nullable: false);
    $table->morphKey('connectable', $keyType, nullable: false);
    $table->jsonb('permissions');
    $table->string('status')->default('accepted')->index();
    $table->jsonb('meta')->nullable();
    $table->timestamp('expires_at')->nullable();
    $table->timestamps();
    $table->softDeletes();

    $table->unique(
        ['connector_type', 'connector_id', 'connectable_type', 'connectable_id'],
        'connections_morph_unique',
    );
});

UUID and ULID keys

Both morph id columns follow key_type — bigint (the default), uuid or ulid. Set it before publishing and running the migration: it is fixed once the table exists, and the bigint default produces exactly the columns of Laravel’s own morphs().

# .env — set before publishing and running the migration
CONNECTIONS_KEY_TYPE=ulid

php artisan vendor:publish --tag="connections-migrations"
php artisan migrate

One row per pair

The connections_morph_unique index covers connector_type, connector_id, connectable_type and connectable_id — soft-deleted rows included. Connecting the same pair again updates the existing row instead of adding a second one, and a disconnected or pruned pair is revived in place — connect() starts it fresh, reconnect() restores it as it was (see Toggle, reconnect & restore).

permissions and meta are jsonb columns. On PostgreSQL that makes them comparable and indexable; on MySQL and SQLite the schema builder compiles them to the same type as json.