Three levels of engagement, each covering the public brand, the operating portal and the systems that connect them. Native applications and campaign management are quoted as separate work.
Our remit covers the whole operating brand of a venue or institution: the public website people find you through, the program merchandising that reflects how you actually sell, the admissions that feed daily operations, and the portal your staff works in. It also covers the infrastructure nobody puts in a brochure, from domain email and Google Workspace to the CRM behind every enquiry, policy pages drafted for your jurisdiction, consent governed analytics, support desks, and assistants that hand the conversation to a person when it needs one.
We take on a limited number of partners at any one time. Engagements are structured on milestones, measured code volume and a mandatory platform care retainer, because a system of this size stays reliable only while it is maintained. Organizations looking for a single delivery with no continuing relationship will be better served elsewhere.
Royal, Titan and Celestial are not marketing labels. They fix the perimeter of the web build, public site and management portal, and the band of code volume we commit to deliver. Every additional module, integration, or native application appears in the proposal with its own fee and milestones, because a Ninera quote must read clearly for whoever signs it and whoever implements it.
Code volume is measured as work is delivered, which is how a band is confirmed. A complete estate, with admissions, CRM, integrations and policy work, frequently passes 100,000 lines before any mobile development begins.
Eleven workstreams, priced when you need them. Some are absorbed into Titan or Celestial; the rest always appear as a line of their own in the proposal.
How you are found, and how demand reaches your team.
Identity, policy, support and the movement of money.
Going live cleanly, then measuring what actually works.
The figures below are build baselines for the web platform, meaning the public site and the management portal. CRM depth, legal packages, growth setup and native applications are quoted as separate lines once the scope audit is complete.
Foundation
The public brand and the portal your team works in every day.
up to roughly 35,000 lines of code after the scope audit.
Expansion
For when programs, admissions and staff work all run on one system.
between roughly 35,000 and 100,000 lines of code.
Estate
Several applications, deep integrations, and fees set after a technical audit.
beyond 100,000 lines of code, quoted individually.
Placement in a band is confirmed by an audit of code volume as delivery progresses. Estates that carry admissions, CRM and substantial integration work generally settle in Titan or Celestial well before any mobile development is considered.
Software does not stand still once it is live. The mandatory platform care retainer covers patching, backups, certificate management, and incident response, sized to the codebase it protects. It also includes Paladin: we do not leave your estate on hosting firewalls alone. We add hardened perimeter controls, monitoring we operate ourselves, and response when something moves wrong. No security plugin to renew, no separate subscription that quietly lapses. A digital home in our care is watched by systems that stay alive because we maintain them.
Web engagements do not include iOS or Android. Each application is a build in its own right, ordinarily between €2,000 and €10,000 according to the depth of the work.
From €2,000per application
One well defined journey for members or customers, kept in step with the portal.
From €5,000per application
Bookings, forms and authenticated access, with live data available away from the desk.
From €10,000per application
Tools for staff on the floor, covering guests, walk ins, events and payments taken on site.
Our Operations level applications are built for the working day inside a venue: walk ins, guest capture, events and payment taken on the spot through Stripe, using tap to pay where the device supports it and emailed payment links where it does not, all synchronized with the portal.
What follows is the work we carry out in the field. The scope audit turns it into line items and fees.
A good number of engagements start on WordPress or a similar CMS. We move everything we can reach, the database included, and bring it back online on a codebase you own.
Policy documents are drafted around your programs and the jurisdictions you operate in, then approved by the competent regulatory bodies.
Operational data is modeled on the way your team works, rather than on the constraints of an off the shelf platform.
Paladin is the security layer inside platform care. It protects the estate from intrusion without asking you to buy another product every year.
The connections we build most often on a complete estate. Language model features go in where they improve a workflow and stay out where they do not.
Academies and venues, professional practices, commerce, membership organizations and hospitality.
This sits outside the platform build and outside the one off installation of tags. It covers running the campaigns, building the landing pages, feeding the CRM and reporting on the result, on an optional monthly retainer alongside platform care.