About-NR
-
NanoReash
One platform. However many sites run on it.
What it does
NanoReash takes complex, fragmented web structures — scattered logic, distributed functions and dynamic processes — and brings them together into fast, responsive applications that work consistently across devices.
In continuous development since 2006.
Separate outside. Together underneath.
Every site keeps its own identity — its own domain, design, content, language, taxonomy and currency. From the outside they can be completely unrelated. Underneath, they run on the same platform.
That means a platform improvement made once can benefit every site that should receive it.
Adding another site isn't starting again. There is no separate platform to install, no separate system to maintain and no additional technology stack to manage.
Complete, but not closed.
Everything required to operate a NanoReash site is already part of the platform. When a project needs something external, NanoReash can connect to third-party services, APIs, libraries and technologies at the application level without making them part of the platform's core.
Fully managed. With a real person.
Nothing to install, patch or keep current. Hosting, updates, security and maintenance are carried as part of the licence.
Whether you're running a standard NanoReash application or a custom application built specifically for your organisation, it remains part of the same continuously evolving platform.
NanoReash has never simply abandoned an earlier generation and started again. Sites built years ago are still running and still supported, while the platform continues to evolve underneath them.
Today, improvements can be delivered through automatic updates designed to keep the platform current without interrupting your work.
No limits. No lock-in.
Developer and EDU licence holders have no artificial cap on pages, products or locations. Content volume was never the right thing to measure — so it isn't.
Your sites, content and business data remain with the licence holder and can be exported when required.
Nothing gets left behind.
NanoReash has never been treated as disposable software. Earlier generations have been evolved, modernised and maintained rather than simply switched off.
Backward compatibility costs something to maintain — and we believe that cost is worth carrying. The work you've already invested in shouldn't become obsolete simply because the technology underneath it has improved.
-
Technical Introduction
Overview
NanoReash is a self-contained PHP web operating platform in continuous development since 2006. It was not built on an off-the-shelf framework and is not an extension of an existing CMS.
It operates as a managed platform. What follows describes the technology a site runs on — not a collection of software that a licence holder is expected to install or maintain.
Dependencies & integration
The NanoReash core operates without Composer, namespaces, autoloaders or third-party framework dependencies.
This keeps the core under NanoReash's control rather than making the platform dependent on an upstream package chain that can become abandoned, incompatible or vulnerable.
Nothing external is required — and nothing external is prohibited. Applications can integrate with third-party frameworks, libraries, services and APIs at the application layer where required.
Multi-site architecture
Multi-tenancy is resolved at the data layer rather than through maintaining parallel installations.
Shared tables carry tenant identifiers that scope data access, allowing multiple sites to operate through one underlying codebase while remaining logically separated.
One codebase means a platform-level improvement can be applied once rather than maintained independently across every installation. Layout, design and theming resolve independently for each site, allowing completely different websites to operate on the same platform.
Data access & security
Database access is handled through a centralised query layer using prepared statements throughout, with a cached connection per request.
Output escaping and URL whitelisting are enforced at platform level, making core injection and XSS protections properties of the platform rather than something dependent on whoever last edited a page.
Servers operate behind active intrusion detection and firewall integration, with security updates applied at host level across the environments they serve.
Infrastructure
NanoReash environments run on dedicated infrastructure with high-performance striped mirrored storage, provisioned so that storage I/O is not unnecessarily imposed as the limiting factor under load.
Hosts are not intentionally oversubscribed. Capacity follows the underlying environment rather than being artificially restricted through software-based content limits.
Development model
NanoReash evolves rather than repeatedly starting over.
Components are refined, modernised and replaced where appropriate while the underlying platform continues forward. Legacy components can be retired without abandoning the applications that depend on the platform.
Backward compatibility is maintained deliberately, allowing sites built on earlier generations of NanoReash to remain in production while the platform around them continues to advance.
Licensing model
NanoReash is licensed by environment — whether that means a single site, a group of sites or a complete server — with hosting, maintenance and security updates carried underneath the licence.
Ten years ago, a licence could be $10,000 and run one site because a host typically ran one site. The terms were not rewritten every time the technology underneath them changed.
Since then, hardware, storage, networking, virtualisation and NR WebCore have transformed what a single environment can support. A licence originally purchased for one site can now operate across a complete multi-site environment, each site retaining its own domain, design and TLS configuration.
The technology improved. The value of the licence stayed with the licence holder.
New licences start at $299 on the same principle.
The NanoReash core platform, architecture and source framework remain part of NanoReash and are licensed for use rather than transferred. Multi-host environments, data-model access and specialised integration work can be arranged separately.
-
For Developers
Build on it. Manage clients on it. Charge your own rates.
The arrangement
A NanoReash licence can be held by a developer or agency rather than by the end client. Sites are built and operated on NanoReash while the client relationship and ongoing services remain entirely with the developer.
What you charge your clients — monthly management, content updates, SEO, hosting, development, per-page services or anything else — is determined by you.
NanoReash sets those prices and does not compete for those clients.
Why the model works
Content volume is not metered. A growing client site does not suddenly hit an arbitrary page limit or require a new software tier.
A server licence can cover every NanoReash site running within that environment, allowing the cost per client site to decrease as your client base grows.
Adding another client becomes a configuration exercise rather than rebuilding the technology stack from scratch.
One underlying platform means one maintenance burden — not twenty separate installations to patch, update and manage.
What is supported
Your dedicated NanoReash representative supports the licence holder, not the licence holder's clients.
You remain the technical and commercial face your clients deal with, while NanoReash supports the platform underneath you.
Hosting, security, platform maintenance and updates are carried underneath the licence.
That leaves you focused on the work that actually creates value: building, designing, developing, selling and managing.
What stays with NanoReash
Everything you build within the environment remains with the licence holder — including sites, content, configuration, applications and client data.
The NanoReash core platform and source framework remain licensed technology rather than being transferred.
Co-beneficial arrangements and expanded access are available under partner terms.