FAQ
Frequently asked questions
Clear answers on compliance, security, hosting, IP, and how implementation works so you know exactly where you stand before and after you sign.
Compliance, Security & Operations
Platform architecture, hosting, licensing, IP, and how we manage ongoing security and support.
What is the platform built on?
The portal is built on React and TypeScript. The exact stack, supported components, and scope are set out in the SOW.
Where is the portal hosted?
We deploy into a managed cloud environment designed for production use. The hosting provider and environment design are confirmed in the SOW.
Do we need any licences to run it?
Usually there are no special licences required just to run the portal itself. Any third-party costs around identity, messaging, monitoring, storage, or similar depend on your configuration and are itemised in the SOW.
Who owns the intellectual property (IP)?
There are two parts:
- Core platform IP — our underlying framework and reusable components — stays with us.
- Client-specific deliverables — anything built specifically for your implementation and funded by you — is assigned to you.
If we fund enhancements or custom modules, do we own that code?
Yes. If you fund bespoke enhancements for your implementation, ownership of those deliverables is assigned to you as defined in the SOW. We retain ownership of any pre-existing or background components used to deliver them.
Is the source code stored in a repository?
Yes. Source code is maintained in a standard version-controlled repository. Access, export rights, governance, and any escrow-style arrangements are set out in the SOW.
If Luminair stopped operating, could we keep the system running?
Yes. The commercial terms can include continuity provisions so you can transition development and support to another provider if needed, subject to the release conditions defined in the SOW.
What does "maintenance" include?
Maintenance typically covers routine updates, security patching, dependency management, and release support. Scope, SLAs, and exclusions are defined in the SOW.
Are upgrades included?
Upgrades are included within the agreed maintenance scope. The cadence, version policy, and any major upgrade approach are documented in the SOW.
Do you do penetration testing or vulnerability scanning?
We run ongoing vulnerability management, including scanning and patching, as part of maintenance. Independent penetration testing can be included where required and is specified in the SOW.
Are there offshore developers or support staff with access?
System access is restricted to authorised personnel and governed by least-privilege controls and auditability. If offshore access is involved, it is controlled under the same security and contractual requirements and disclosed in the SOW.
What are the typical ongoing costs?
That depends on the configuration you choose. Typical ongoing costs can include hosting, monitoring, identity, email or SMS, and other optional services. We set out expected operating costs and responsibilities in the SOW.
Can you provide an overview of security, hosting, and support before we sign?
Yes. Before signing, we can walk you through the operating model: hosting, access controls, release process, support model, and responsibilities. Final commitments are captured in the SOW.
Portal & Implementation
How each portal is built, what can be customised, what we need to get started, and how data and ownership work after launch.
What is a portal instance?
Each portal is delivered as a firm-specific implementation. Branding, structure, permissions, content, and connected workflows are configured for the business rather than delivered as a standard product with your logo on it.
Is the portal customised for each firm?
Yes. Each implementation is built around the firm it is for. The exact level of configuration and custom development depends on scope, but the portal is always set up around the firm’s requirements and operating model.
What can be customised, and what stays maintained by Luminair?
Client-facing elements can be configured for the firm, including branding, navigation, modules, workflows, roles, and integrations. The underlying backend logic, shared platform patterns, and maintainable core components stay with Luminair so the platform remains stable, supportable, and easier to maintain over time.
What do you need from our team to get started?
Usually we need the core inputs upfront: branding assets, user types and access rules, target use cases, source data, and any systems that need to connect. The exact requirements depend on scope and are worked through during discovery.
Can the portal integrate with our existing systems?
Yes, where suitable APIs, access, and documentation are available. Integrations are commonly scoped around identity, CRM, document workflows, analytics, and other business systems. Final integration scope is confirmed during discovery and documented in the SOW.
Can existing users, data, or content be migrated?
Yes, in many cases. Migration can include users, roles, documents, records, and other content, depending on the quality, structure, and accessibility of the source data. The final migration scope is assessed during implementation.
How long does implementation usually take?
That depends on what is being delivered. Simpler implementations move faster. Projects with integrations, migration, and custom workflow requirements take longer. Timing is confirmed through scoping and documented in the SOW.
What does support look like after launch?
Support typically covers maintenance, updates, issue resolution, and an agreed path for ongoing improvements. The exact support model, response expectations, and scope are set out in the SOW.
What does ownership look like after launch?
You retain ownership of your business data, branding, and client-specific deliverables as defined in the SOW. Luminair continues to maintain the underlying backend logic, shared platform components, and retained core intellectual property under the agreed service model.
How is data handled and secured?
Data access is controlled through role-based permissions and standard security practices across the application and hosting environment. The exact security model, responsibilities, and any client-specific requirements are set out in the SOW.