Product
Lihok Frontline
An intelligent front office for your business. Live in production today.
Businesses that generate demand through their own website and want it to work — and to stay answerable for what it says.
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 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.
Once our enquiry form is connected, we will walk you through the live platform and show you exactly which parts are finished.