Elementary Interactive

Technical specifications

Written for the people who have to assess this, not for the people who have to sell it.

Longevity

Security fixes appear in the actively maintained major versions of the components a platform is built on. A system that has drifted onto an unmaintained version has two options when an advisory lands: backport it, or migrate under pressure. Both happen at the worst possible moment.

The platform runs on established, actively maintained technologies with years of production use and a large contributor base. Security patching is part of maintenance rather than scheduled work.

Modular architecture

The platform comprises more than twenty independent packages. Each has its own versioning, test suite and deployment cycle. A content update doesn't require rebuilding the operations module; a security fix doesn't touch the event layer.

This isn't a monolith split into folders — each module declares its own dependencies and can be installed, updated or replaced independently through Composer. Customisations survive upgrades because they live in separate packages, not inside the core.

Core packages: authentication and tenancy, base models, API access, audit and versioning, content management, media management.

Domain packages: forms, events, news, knowledge base, documents, tags, operations, AI, webhooks.

Two major platform versions have been delivered to date. The migration cost of the second was carried by us, not by clients.

Minimal external dependencies

The platform uses about ten production dependencies beyond the framework itself. Every one of them is well maintained, widely used, and has a clear single purpose. No experimental frameworks, no packages abandoned by their maintainers.

Laravel Sanctum

First-party API authentication, maintained by the framework's core team.

Laravel Reverb

First-party WebSocket server, maintained by the framework's core team.

Maatwebsite Excel

Enterprise spreadsheet processing with encryption support for sensitive data exports.

Spatie packages

The most widely used Laravel package ecosystem, in production in thousands of applications.

Multi-tenancy and data isolation

Every request is scoped to a company and a site. Data isolation is enforced at the database level, not only in application logic.

Multiple websites or applications can run under one company, each with their own content, media and configuration. Each tenant can operate on a dedicated database, with credentials encrypted at rest and decrypted only at connection time.

Tenant isolation applies consistently across HTTP requests, background jobs, CLI commands and WebSocket connections. A queued job cannot reach another tenant's data.

Authorization

Access control is policy-based, covering every model and operation — create, read, update, delete — enforced at the framework level. The administration interface automatically respects these policies: users only see what they are authorised to access.

Granting or revoking access takes effect without requiring a deployment.

Audit and change tracking

Every model change is tracked automatically — who made it, when, from which IP address, and what exactly changed, field by field, with previous and new values. Login and logout events are recorded with IP address and user agent.

Content supports draft and publish workflows with up to ten stored versions per record. Any previous version can be restored in one step.

Audit logs are pruned after 365 days by default, and the retention period is configurable.

GDPR compliance details

Background processing and real-time notifications

Long-running operations — bulk updates, imports, media processing — run as background jobs with automatic retry logic and structured logging. Failed jobs retry three times with exponential backoff.

Users receive real-time notifications over WebSocket when an operation completes. Every job logs its full context — operation type, model, user, tenant — in structured form, so it can be read by standard log aggregation and alerting tools.

Testing and code quality

More than thirty test files across the packages cover unit, feature and integration scenarios, including security-specific tests: tenant isolation, policy enforcement, upload validation and authentication events.

Code formatting is enforced automatically on every change against the PSR-12 standard, and the test suite runs with strict type checking.

FAQ

The platform comprises 20+ independent packages, each with its own versioning, test suite, and deployment cycle. A CMS update doesn't require rebuilding the ERP module. A security fix doesn't touch the event management layer. Customizations survive upgrades because they live in separate packages, not inside the core — so new features arrive without breaking existing functionality.

The platform runs on any Docker-compatible host: bare metal, VPS, AWS, Azure, GCP, or on-premise. No cloud vendor lock-in, no proprietary runtime fees. All production dependencies beyond Laravel are open-source with permissive licenses.

Every request is scoped to a company and site. Data isolation is enforced at the database level — not just in application logic. Each tenant can operate on a dedicated database, with credentials encrypted at rest and decrypted only at connection time. Isolation applies consistently across HTTP requests, background jobs, CLI commands, and WebSocket connections. A queued job cannot accidentally access another tenant's data.

The platform integrates with Sentry for error tracking, Grafana + Loki for log aggregation, Papertrail for cloud log management, Slack for real-time critical alerts, and any syslog-compatible monitoring solution. A dedicated /up health check endpoint integrates with load balancers and uptime monitoring services out of the box.

Everything above runs on infrastructure we operate.

Hosting

Response times and support.

SLA and Support