Skip to content
Lihok TechnologiesOPC— home

Product

Lihok Frontline

An intelligent front office for your business. Live in production today.

Available now

Businesses that generate demand through their own website and want it to work — and to stay answerable for what it says.

In plain terms

Software that gives a business a real front office on its own website. It passes each enquiry through to the business instead of losing it, and it answers from the company's own approved information rather than making things up. The part that answers with AI on its own is still being developed.

Shared foundation

Lihok Frontline · Available now

Designed to draw on Lihok Intelligence

Designed to draw on interaction and knowledge capabilities — conversation, the tenant's own governed knowledge, and customer-facing decision assistance. What is live today is the front office, the governed knowledge projection and structured intake; the AI answering capability is still in development.

  • Knowledge
  • Reasoning
  • Interaction

This is architecture rather than a delivered integration. What a product may actually draw on is decided per request — by the product, the organisation, the person, their permissions and the governance in force — and by what has been built.

How the shared layer works

Frontline is a multi-tenant platform, not a template. Each tenant gets its own governed knowledge source, its own public front office, its own branding and its own administration — with isolation enforced at the persistence boundary rather than by convention.

The structure behind the site

How Lihok Frontline is put togetherThe same structure at mobile width. A visitor reaches a public business site, behind which two tenant boundaries sit side by side holding their own content. Both feed one governed knowledge layer, which branches into an answer surface marked in development, an enquiry and a service request. The enquiry and service request run into the business.VisitorPublic business siteTENANT CONTENT, KEPT SEPARATETenant ATenant BGoverned knowledgeAnswerin developmentEnquiryServicerequestThe business
  • Public site
  • Tenant content
  • Governed knowledge
Each tenant's content sits inside its own boundary rather than beside its neighbour's, which is what multi-tenant means here. The answer surface is marked in development because it is not generally available: until a tenant's own provider credential is configured the platform serves a governed fallback rather than simulated conversation. It is also the one output with no path into the business, for the same reason.

The problem

A conventional website answers nothing and qualifies no one. It cannot tell a serious buyer from a casual visitor, it cannot answer the questions people actually ask, and it loses the intent behind every visit it doesn't convert.

What is live, precisely

Frontline is deployed and running for a live tenant, whose public website is served by the platform today. We do not name our customers here.

The platform itself — the site engine, the governed knowledge layer, the inquiry service and the administration console — is in production. The AI answering capability is not. It is in development, and it is labelled that way everywhere it appears.

Capabilities

What you can use today — and what you cannot.

Both columns matter. The right-hand one is the reason you can trust the left-hand one.

Available now

  • Governed company knowledge

    One canonical knowledge source per tenant. What the platform may say is determined by governance, not by what a model happens to generate.

  • Public front office

    A complete tenant site rendered deterministically from governed configuration — pages, routing, search metadata and structured data.

  • Structured service-request intake

    Visitors submit a structured request that routes to a destination the tenant owns. If that destination is missing, the build fails closed instead of silently discarding the submission.

  • Tenant administration console

    Tenant administrators manage their own knowledge, content, branding and readiness. Cross-tenant administration is not possible, and credentials are write-only.

  • Genuine multi-tenant isolation

    Tenant context comes from trusted server-side context and is enforced at the persistence boundary. Cross-tenant retrieval is rejected by construction.

  • Truthful readiness reporting

    A declared capability is reported separately from a runtime-ready one. When a required dependency is absent the platform fails closed and says so.

  • Knowledge answers, actions act

    An outcome such as an approval, a price or a booking may be asserted only after an authorised action tool has actually returned success.

Not available yet

  • AI answering

    The grounded assistant is in development. Until a tenant's own provider credential is configured, the platform serves a governed fallback rather than simulated conversation. We do not show you a demo chat we cannot stand behind.

  • Voice and telephony

    Planned. Not currently available.

  • Scheduling

    Planned. The platform fails closed with 'no live calendar' until an authoritative scheduler exists.

  • Document and image intake

    Planned. Not currently available.

  • Broader external integrations

    Planned. Not currently available.

Commercial model

Per tenant, by subscription.

Each tenant gets its own governed knowledge, its own public front office and its own administration. Pricing depends on what you need, so we discuss it rather than publishing a number that would not fit.

See it running, then decide.

We will walk you through the live platform and show you exactly which parts are finished.

Request a demo