Nanoreash Charter
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 whole platform, not a cut-down version of it.
At its core it is the black hole of web execution: where complexity becomes order.
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 run on it.
What it does
NanoReash takes complex, fragmented code structures — scattered logic, distributed functions, dynamic processes — and resolves them into fast, responsive applications that work the same on every device.
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.
We never abandoned old versions, some they're still up as legacy sites, though now a day on the new framework and continuously improving our system with automatic updates that don't interrupt your work.
No limits, no lock-in
Developer and EDU License Holders - have 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 exported 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. More commonly now a day though, the licence holder will be notified* of an update notification, no restart required.
-
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 — what follows describes what a site runs on, not anything a licence holder installs or maintains.
Dependencies and integration
The core runs without Composer, namespaces, autoloaders or third-party framework dependencies — so there is no upstream package to go unmaintained, 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 the core never inherits 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, so 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 — injection and XSS defences are properties 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 — retiring unused classes, replacing legacy components, modernising alongside browser and standards changes. Backward compatibility is maintained deliberately, so sites built on early versions remain in production today.
Licensing model
Licensed by environment: a site, a group of sites, or a complete server, with hosting, maintenance and security updates carried underneath.
Ten years ago a licence was $10,000 and ran one site, because a host ran one site. The terms have not been rewritten since; everything underneath them has. Hardware, storage, networking, virtualisation and NR WebCore now put many sites on a single host, each with its own domain, design and TLS handling. A licence bought to run one site now runs a full multi-tenant environment, at the price it was bought for.
That is where the value sits — never repriced, never re-tiered, never capped, so a decade of advances accrued to the holder instead of arriving as a new invoice. New licences start at $299 on the same principle.
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 and the ongoing work stay with the developer.
What is charged downstream — monthly management, content updates, SEO, hosting, per-page rates, whatever the market will bear — is set by the licence holder. NanoReash sets none of it, and never contacts or contracts 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 in that environment, so the cost per client site falls as more are added.
Adding a client is a configuration change rather than a build, and 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.
Platform, hosting, security and updates are carried underneath. The 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 are licensed for use rather than transferred.
Co beneficial arrangements and expanded access are available under partner terms.