Elementary Interactive

Where Nitrogen runs

Not a hosting product. The infrastructure the platform runs on, operated by the team that built it.

One team, one line of responsibility

We don't host other people's systems. This page describes where the platform we build and maintain actually runs — and why that isn't a separate supplier relationship.

When a site is slow, the cause is somewhere between the code, the database, the cache and the network. With separate suppliers, that question becomes a negotiation. Here it doesn't: the same team is accountable for the application and for the infrastructure it runs on.

Where the data is

A data centre in Budapest, on hardware we own and operate. Hungarian jurisdiction, not a European region of a platform owned elsewhere.

For an organisation that has to answer where its data physically sits, and under whose law, that is a shorter answer than most suppliers can give.

All the way down

One team is accountable for the application, the infrastructure it runs on, and the machines underneath. There is no third party in the chain where an answer can stall.

Builds and deployments run on our own pipeline. That is what makes “security patches applied as part of maintenance” a routine operation rather than a scheduled project.

Resilience

The platform runs on three enterprise servers in the Magyar Telekom data centre in Budapest, on hardware we own.

Redundancy at every layer: dual independent power feeds per machine, two network uplinks on separate switches, redundant stateful firewalls, and services distributed across all three machines rather than pinned to one. A machine can fail without the platform going down.

Storage is SSD-based RAID, replicated across machines. Backups run daily on site, with encrypted off-site copies held in a second Hungarian data centre. Both primary and backup data remain under Hungarian jurisdiction.

What the licence includes

None of these is a line item you add later. Infrastructure is part of the platform, because the platform is not something you deploy yourself.

Infrastructure

Compute, storage and network, sized to your estate.

Content delivery

Assets served through our own CDN, on signed, expiring URLs.

Backups

Automated, tested, restorable to a point in time.

Monitoring

Availability and performance, watched rather than reported.

Updates

Security patches and platform versions applied as part of maintenance.

Certificates and domains

Issued, renewed and monitored.

What we don't do

We don't take over existing systems built by someone else, and we don't sell infrastructure on its own. Both would break the thing that makes this work: that one team is responsible for the whole of it.

If you need hosting without the platform, we're the wrong supplier — and we'd rather say so here than after a proposal.

Availability targets and response times are defined by priority: SLA and Support. What the platform is built on: Technical specifications.