Nanoreash Charter
NanoReash is a system designed to create fast, smooth web applications that work seamlessly across all devices. It takes complex code structures, simplifies execution, and transforms them into intuitive, responsive user interfaces.
At its core, NanoReash is the black hole of web execution — where complexity becomes order. It draws in fragmented logic, distributed functions, and dynamic web processes, transforming them into consistent, high-performance applications.
Its value comes from:
- A mature architecture
- Deep system integration
- Long-term development knowledge
- The ability to adapt as business requirements change
-
NanoReash
One platform. However many sites are running on it.
What it is
A platform for managing many websites, applications and locations from one place. Built for people running more than one site — though a single site gets the same platform at full size, not a cut-down version of it.
In continuous development since 2006.
Separate outside, together underneath
Each site keeps its own domain, design, content, language, taxonomy and currency. From the outside they are unrelated. Underneath they run on the same platform, so a change made once lands everywhere it should.
Adding a site is not starting again. No separate account, no separate billing, nothing further to keep track of.
Complete, but not closed
Everything needed to run a site is already part of the one platform. Where a project calls for something outside — a third-party framework, an external service — it links in without a fight.
Fully managed, with a real person
Nothing to install, patch or keep current. Hosting, updates and maintenance are carried as part of the licence.
Every licence includes a dedicated representative — from a single site upward, not held back for the larger ones. Student and concession licences use an online help base instead, which is still being developed.
No limits, no lock-in
No cap on pages, products or locations. Content volume was never the right thing to measure, so it isn't measured.
Sites, content and business data belong to the licence holder and can be taken away at any time.
Nothing gets left behind
NanoReash has never been abandoned and rebuilt. Sites set up on early versions are still running and still maintained.
Backward compatibility costs something to keep, and it is kept — because the alternative is telling people the work they paid for no longer counts.
-
Technical Introduction
Overview
A self-contained PHP web operating platform, in continuous development since 2006. Not built on an off-the-shelf framework and not an extension of an existing CMS.
It is operated as a managed platform, not distributed for licence holders to install or run themselves. What follows describes what a site runs on, not what is delivered.
Dependencies and integration
The core runs without Composer, namespaces, autoloaders or third-party framework dependencies — so no upstream package can be abandoned, break on a minor release, or be compromised at source. Upgrading stays a decision rather than something forced by an end-of-life.
Nothing external is required; nothing external is prohibited. Applications link to third-party frameworks, libraries and APIs at the application layer, per deployment, so a project gets what it needs without the core inheriting a dependency chain on behalf of every other tenant.
Tenancy model
Multi-tenancy is resolved at the data layer, not by parallel installations. Shared tables carry a tenant identifier that scopes every query, so all sites run through one codebase while staying isolated from one another.
One codebase is patched regardless of site count, and a platform-level fix reaches every tenant at once. Layout and theming resolve per tenant at render time, so visually unrelated sites are served from shared templates without forking.
Data access and security
A single cached connection per request, through a centralised query layer using prepared statements throughout. Output escaping and URL whitelisting are enforced at framework level rather than left to page code — injection and XSS protection is a property of the platform, not of whoever last edited a template.
Servers run behind active intrusion detection with firewall integration. Security updates apply at host level, across every tenant that host serves.
Infrastructure
Bare metal with striped mirrored storage, provisioned so disk I/O is not the constraint under load. Hosts are not oversubscribed.
This is the basis for licensing by environment: capacity follows the hardware, not an artificial content limit imposed in software.
Development model
Evolutionary. Components are refined rather than replaced wholesale, and backward compatibility is maintained deliberately so long-running deployments are never stranded on an unsupported version.
The platform's second decade has focused on refinement — retiring unused classes, replacing legacy components, modernising alongside browser and standards changes. Sites built on early versions remain in production today.
Licensing model
Licensed by environment: a site, a group of sites, or a complete server. Content volume is not metered. Hosting, maintenance, security updates and a dedicated representative are included from a single site upward.
Early licences were issued when a single server supported far fewer sites. Advances in hardware, storage, networking, virtualisation and NR WebCore mean the same licensed environment now supports substantially more. The terms have not changed; the capacity behind them has.
Assets created within an environment belong to the licence holder and remain exportable. The core platform, architecture and source framework remain part of NanoReash, licensed for use rather than transferred. Multi-host environments, data model access and integration work are arranged separately.
-
For Developers
Build on it, manage clients on it, and charge your own rates.
The arrangement
A licence can be held by a developer or agency rather than by the end client. Sites are built and run on NanoReash; the client relationship, the pricing and the ongoing work stay with the developer.
What is charged downstream — monthly management, content updates, SEO, hosting, per-page rates, whatever the market takes — is set by the licence holder. NanoReash does not price, contact or contract with those clients.
Why the licensing works for it
Content volume is not metered, so a client site is never capped at an arbitrary page count and never triggers an upgrade for growing. A server licence covers every site running in that environment, which means the cost per client site falls as more are added.
Sites are provisioned as a configuration change rather than a fresh installation, so adding a client is minutes rather than a build. One codebase is patched for all of them at once — twenty client sites carry the maintenance load of one.
What is supported
The dedicated representative supports the licence holder, not the licence holder's clients. That is the point: one technical contact who knows the environment, so the developer stays the only face their clients ever deal with.
The platform, hosting, security and updates are carried underneath. Skills required are the ones worth having — building, designing, selling and managing — rather than server administration and patch cycles.
What stays with NanoReash
Everything built within the environment belongs to the licence holder: sites, content, configuration, applications, client data. The core platform and source framework remain part of NanoReash and are licensed for use rather than transferred.
Co-branding, revenue-share arrangements and expanded access are available under partner terms.