(The platform) · OliveCore · born on .NET Core
Built, not assembled.
OliveCore is the platform behind every neo optic build - conceived, written and evolved by us through three generations of Microsoft's web platform. Owning the platform outright, rather than renting a builder, is rare - and here is why it matters to you.
Most websites are assemblies of parts nobody in the room actually made. When a part fails, you inherit the consequences.
OliveCore is the other way of doing it. One platform, one team, every line accountable - sharpened on real client work, from one-page brochures to systems serving organisations worldwide - with a lineage running back to our first builds. When we build on it, we are not hoping someone else's parts hold. We wrote the parts.
(A true story - names withheld)
The invoice that explains everything.
A local business came to us with a story we have heard many times. Their site - built by another agency on WordPress - used a popular form plugin. The agency chose it. One day a serious vulnerability was found in that plugin, and the agency wrote to say: the component we selected for your site is now insecure - pay us to replace it, or carry on knowing your site is exposed.
Read that again. A part they picked, failing through no fault of the client, became the client's emergency and the client's bill. Nobody explains this risk on the way in - it only gets explained when it bites.
We could not send that letter if we wanted to. We chose every layer OliveCore stands on - so when any of it needs fixing, that is our job, not your surprise invoice.
OliveCore vs the rest.
| OliveCore | WordPress agencies | DIY builders | |
|---|---|---|---|
| The foundation | Ours, built since 2000 | Rented from the WordPress project | Rented from the builder |
| How your site is made | Engineered for you | Assembled from third-party plugins | Template plus drag-and-drop |
| When a component fails | Our problem, our fix - warranty as standard | Frequently your invoice | You wait and hope |
| Public plugin attack surface | None to probe | Vast, public, and the main way in for attackers | Closed, but shared by millions |
| Who answers for it | One Norwich team, one phone number | Agency, plugin authors and hosts - a chain of shrugs | A helpdesk queue |
| Accessibility | Built to WCAG 2.2 AA and fixable at source, not a bolt-on | A plugin, if anyone remembers | Whatever the template did |
| Ready-made add-ons | Fewer - we build what you actually need | A plugin for everything | An app store |
| Cost on day one | More than a template | Mid-range | Cheapest by far |
| Cost over five years | Engineered once, owned properly | Plugin licences, patches, rebuilds | Subscriptions forever |
| If you move agency | Your data exports; OliveCore can be licensed | Portable between WordPress shops | Your site stays behind |
Every option has pros and cons - ours included. The difference is whose problem the cons become.
(Already elsewhere?)
Already on WordPress?
You're not stuck there. We can bring your content, media and site structure into OliveCore - automatically where the source is clean, carefully rebuilt where it isn't.
The result is a faster, more accessible website on a platform we own and can change, without carrying across years of theme, plugin and page-builder baggage. Show us what you've got and we'll map the route across.
Talk to us about moving across(An honest question)
What happens when something breaks?
Because something always, eventually, breaks - in every platform, including ours. The question that decides your next five years is not whether, but whose problem it becomes.
We chose every layer OliveCore runs on - the framework, the database, the lot. So if a layer we chose causes a problem, we could not look you in the eye and call it your bill. Bugs in a build we finished are fixed free under our standard warranty, and the person fixing them wrote the code they are fixing.
Our choices, our problem.
(The question nobody asks out loud)
What if you leave us?
Every proprietary platform carries a quiet fear: am I locking myself in? So let us answer it before you ask. Your content and data are yours and export cleanly. Your domain is yours. And OliveCore itself is available under licence - to organisations, and yes, even to other agencies - so leaving neo optic does not have to mean leaving the platform. That is not a new ambition, either: before the pandemic interrupted them, licensing discussions with other agencies were already underway - and the next generation of OliveCore reopens that door.
Twenty-six years of clients have stayed because the work is good - not because the exit was blocked. We would rather earn next year than mortgage it.
Three generations deep.
Long before OliveCore had a name, our sites ran on our own platform - drag-and-drop “content panels”, as we called them, in the WebForms era. Owning the engine was already the habit.
The platform was rewritten for the MVC generation - same principle, stronger architecture, still entirely ours.
Rebuilt again on Microsoft's then-new .NET Core - which is exactly where the name comes from. Olive, meet Core.
The current generation: modern .NET foundations, a next-generation image pipeline serving lean WebP, block-based page building (the content panels, three generations on), and performance treated as a feature. Still ours, still moving.