Elementary Interactive

Knowledge Base

Where the detail lives. Specifics on the products, compliance, support arrangements, and what implementation actually looks like — organised by topic, written for people who've decided to look closely.

Platform & Architecture

The N platform is the common foundation everything else runs on. These questions cover how it's built, how it's maintained, and what it means in practice to run enterprise infrastructure on a single, coherent codebase rather than a stack of plugins and third-party dependencies.

The N platform is a modular CMS and ERP foundation built on Laravel. At its core sits Central Admin: one interface to manage users, permissions, content, and integrations across all your sites and applications. No scattered logins, no version mismatches, no "which plugin handles that?" moments.

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.

Infrastructure & SLA

These questions cover how the platform is deployed, how it stays running, and what happens when something goes wrong. The short version: it's designed to run itself, and when intervention is needed, the tooling is already in place.

Any Docker-compatible host: bare metal, VPS, AWS, Azure, GCP, or on-premise. There is no cloud vendor dependency in the critical path — authentication, content management, media handling, and background processing all run on your infrastructure.

The platform runs in containerized environments with strict service isolation. Dedicated containers for the application server, database, cache, background workers, and scheduler — each with independent health monitoring and automatic recovery. If a container fails, it recovers automatically without manual intervention.

Routine updates deploy during business hours via container-level rolling restarts. Database migrations are scheduled during low-traffic windows with advance notice. Emergency security patches deploy immediately, regardless of schedule. Users never see a maintenance mode screen.

Failed jobs retry automatically up to three times with exponential backoff. Jobs that exhaust all retries are logged in a dedicated failed jobs table for manual review and replay. Users receive real-time WebSocket notifications when operations complete.

The platform ships with structured logging compatible with any syslog-based tool. Native integrations exist for Sentry, Grafana + Loki, Papertrail, and Slack. The /up health check endpoint integrates directly with load balancers and external uptime monitors. If you run a custom solution, the structured JSON log format is compatible with any monitoring stack that accepts standard input.

Security & GDPR

Enterprise systems handle data that belongs to other people. These questions cover how the N platform controls access, tracks changes, and handles personal data — not as compliance theater, but as practical controls that hold up under audit.

Access control is policy-based, covering every model and operation — create, read, update, delete — enforced at the framework level. The admin interface automatically respects these policies: users only see what they are authorized to access. Roles and permissions are built on Spatie Permission with 24-hour caching; changes take effect without a deployment.

Each form can be configured with an expiry date. Once the form is no longer active, the system automatically begins counting down to the deletion date and purges collected data after the defined number of days. No manual cleanup, no forgotten datasets persisting years after an event.

Any individual form field can be marked as containing sensitive data, regardless of field type. Marked fields are masked in the interface and visible only to authorized data owners. Email address fields are masked by default without any additional configuration.

Any authorized user can be designated as a data owner for a specific form. Data owners are the only users permitted to export submissions or import pre-existing lists. Assignment is done per form in the admin interface.

When a data owner exports form submissions, they set a password at the time of download. The exported file is a non-editable Excel file, encrypted with that password. Only the person who set the password can open it — no one else in the system has access to the export after it leaves.

Yes. Every model change is automatically tracked — who made it, when, from which IP address, and what exactly changed, field by field, with old and new values. Login and logout events are recorded with IP and user agent. Audit logs are automatically pruned after 365 days (configurable).

All data is stored in European data centers. No transfers to third-party servers abroad. No plugins phoning home, no external scripts with hidden data collection.

Content Management

N3 is where editorial work happens. These questions address how content is organized, versioned, and served — and what it means to manage multiple sites, multiple languages, and large media libraries without things falling apart at scale.

N3 manages the full content layer of your organization: menus, pages, documents, media, news, knowledge bases, and FAQs — served through a clean API to any frontend or integration that needs it.

Every edit is recorded automatically — who changed what, when, and exactly what was modified, field by field. Any previous version can be restored with a single click, not just the last save, but any point in the content's history. Retention policies are configurable per content type.

Yes. A single N3 installation can serve multiple websites or applications, each with their own content, media, and configuration, all managed from Central Admin. A marketing team member can manage one site's blog without seeing another site's content.

Images, PDFs, videos, and documents — all stored in a single searchable library, organized into folders by content area and filterable by file type. Files can be found by name or alt text.

Upload a source image once. The system automatically generates every size variant needed across the site — thumbnail, small, medium, large, extra large — each with its own breakpoint. No manual resizing, no inconsistent sizes across pages.

Yes. The system tracks which variants are auto-generated and which have been manually overridden. Any variant can be reset to the automatically generated version at any time.

Files are scoped to a site by default — only accessible within that specific site. Company-wide files are available across all sites operating under the same organization. The distinction is set at upload time and can be changed by authorized users.

Business Operations

Content management handles what your organization publishes. Business operations handle what it does. These questions cover the operational modules — forms, event management, and integrations — that connect your digital presence to your internal processes.

N3 Content Management handles the editorial layer: pages, documents, media, news, knowledge bases. N3 Business Operations handles the operational layer: forms with workflow logic, event management, and integrations that connect your website to your business processes.

Yes. Form submissions can be routed to the right people, trigger emails, create tasks, and update records automatically. Forms become the starting point of business processes, not just data collection endpoints.

The full lifecycle: creation, promotion, registration with capacity limits and waitlists, on-site check-in, automated communications (reminders, confirmations, follow-ups by email or SMS), and post-event reporting. One system handles the entire journey.

Yes. N3 modules are designed for integration from day one — REST APIs, webhooks, and pre-built connectors. The platform has been integrated with banks, insurers, and enterprises with complex compliance requirements.

Partnership & Engagement

Whether you're a company looking for a long-term technical partner or an agency that needs reliable backend infrastructure for client work, these questions cover how we work, who we work with, and what starting an engagement actually looks like.

Two types of clients: enterprises that need scalable content and business operation infrastructure managed directly, and agencies that need a reliable technical partner for backend development on client projects.

Yes. We work as the technical backend partner — you handle the client relationship and creative direction, we build and maintain the infrastructure. The arrangement is discreet by default.

Every engagement starts with listening — understanding your business before proposing solutions. You can reach us via the contact form, by email at hello@elementary-interactive.com, or by sending a photograph of your business card. We respond within one business day.

Pricing depends on project scope, scale, and requirements. We don't publish price lists. Submit an inquiry and we'll discuss your specific situation directly.