Zimlix Cloud ERP

Zimlix Cloud ERP started as an internal tool for two distribution clients and grew into the product the company is built around. Every tenant gets its own database, its own branding and a shared codebase that ships weekly.

The brief

Replace a patchwork of spreadsheets and desktop accounting tools with a single system that a five-person company could adopt in a week and a two-hundred-person one could still run two years later.

Key points

• Tenant provisioning with isolated databases and media.
• Role-based back office built entirely with Filament resources.
• Nightly aggregates for finance dashboards.
• Zero-downtime deploys with health checks.

What we built

A tenant-per-database Laravel application with Filament for the back office, Livewire for the operational screens and a reporting layer that pre-aggregates the numbers finance teams ask for every Monday.

Example in code

<?php

namespace App\Models;

use App\Support\Enums\PostStatus;
use Illuminate\Database\Eloquent\Builder;

class Post extends Model
{
    public function scopePublished(Builder $query): Builder
    {
        return $query
            ->where('status', PostStatus::Published)
            ->where('published_at', '<=', now());
    }
}

Outcome

Twelve tenants in the first year, a support load that stayed flat while the customer base tripled, and an onboarding flow that takes a new company from sign-up to first invoice in under an hour.

Simplicity is a feature you have to fight for in every sprint.

Takeaways

Multi-tenancy is a product decision before it is a technical one; isolating tenants early kept both the sales and the on-call conversations short.