Frontend delivery APIs
Headless delivery, route discovery, content detail endpoints, forms, and private sync coverage for frontend teams.
Download markdown
Developer and product playbooks.
Everything your team needs to implement our APIs and master the full LaysanX platform architecture.
This documentation hub covers the entire LaysanX API surface, end-to-end implementation examples, headless delivery flows, and comprehensive technical features for LaysanX. Learn how to upload custom HTML/CSS/JS themes, query the decoupled CMS, configure Lead-to-Ledger automation pipelines, and interface directly with our secure hosted runtime environments.
Featured resources
Everything teams usually need before implementation starts.
Use these entry points when you want the shortest path from review to real integration and go-live verification.
Widget and knowledge base runtime
Bootstrap, ask, and lead flows for the embedded chat widget, with allowed-domain and AI usage behavior.
Download markdownDownloadable Postman collection
Ready-to-run requests for delivery APIs, widget flows, form submissions, private sync, and standalone relay testing.
DownloadTheLiaison reference theme
HTML, CSS, JavaScript, and LaysanX template placeholder starter package for designers building uploadable client themes.
Download theme ZIPReference theme Git repo
Clone or fork the base theme so designers can version their changes before packaging and uploading.
Open Git repoTheme designer guide
Rules, folder structure, placeholders, loops, currency selector, formatted prices, direct pricing checkout, form rendering, and upload workflow for custom theme designers.
Download markdownCoverage and go-live map
Quick reference for current frontend delivery, scoped section layouts, custom sections, redirects, helpdesk, notification engine, widget, billing, AI, custom-domain, and release-ready documentation coverage.
Download markdownProduction release addendum
Launch checklist for the latest client admin, SaaS admin, helpdesk, custom-section, scoped layout, cache refresh, wallet, AI, domain, and documentation changes.
Download markdown
Theme designer guide
Build custom client themes with normal HTML, CSS, and JavaScript.
Designers can start from the finalized TheLiaison reference theme, keep the dynamic placeholders, then upload, preview, and publish their own ZIP package through the theme customization flow.
Designer handoff steps
Download reference theme
Use the TheLiaison HTML/CSS/JS package as the official starter theme and placeholder reference.
Clone from Git
Use git clone https://github.com/laysanx/theliaison-reference-theme.git when designers want version control, forks, or pull-request based review.
Edit normal frontend files
Change `templates`, `sections`, CSS, JavaScript, images, fonts, and layout styles edit in LaysanX Theme editor.
Keep placeholders and loops
Preserve LaysanX template variables like `{{ site.name }}`, `{{ page.title }}`, currency variables, and loops for services, products, blogs, menus, forms, pricing plans, and section controls.
Zip, upload, preview, publish
Package the theme folder as a ZIP, upload it from Client Admin, preview the result, then publish when approved.
Required structure
theme.zip
theme.json
README.md
templates/
home.html
page.html
contact.html
service-list.html
service-detail.html
product-list.html
product-detail.html
blog-list.html
blog-detail.html
sections/
header.html
footer.html
hero.html
services.html
products.html
contact-form.html
assets/
css/style.css
js/main.js
images/placeholder.svg
LaysanX template placeholders
Service card example
{% for service in services limit: section_controls.services.count %}
<article class="service-card">
<img src="{{ service.image }}" alt="{{ service.title }}">
<h3>{{ service.title }}</h3>
<p>{{ service.short_description }}</p>
<a href="{{ service.url }}">View More</a>
</article>
{% endfor %}
Storefront theme example
Currency and direct checkout
{% if currencies.size > 0 %}
<form method="post" action="{{ currency.switch_url | default: '/currency' }}">
<input type="hidden" name="returnUrl" value="{{ routes.current | default: routes.home | default: '/' }}">
<select name="currencyCode" onchange="this.form.submit()">
{% for item in currencies %}
<option value="{{ item.code }}" {% if currency.code == item.code %}selected{% endif %}>{{ item.symbol }} {{ item.code }}</option>
{% endfor %}
</select>
</form>
{% endif %}
{% for plan in pricing_plans %}
<strong>{{ plan.primary_price_formatted | default: plan.price_formatted | default: plan.price }}</strong>
<a class="btn btn-primary" href="{{ plan.checkout_url | default: plan.checkoutUrl | default: plan.direct_checkout_url | default: plan.directCheckoutUrl }}">{{ plan.cta_text | default: 'Buy Now' }}</a>
{% endfor %}
API documentation
Full endpoint coverage with implementation guidance.
These APIs are designed for dynamic websites, headless CMS delivery, standalone frontends, widgets, and operational sync workflows.
Request headers
Public delivery requests require the public key and origin. Private sync also requires the secret key.
X-Public-Key: pk_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Origin: https://www.yourfrontenddomain.com
X-Secret-Key: sk_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxHow to wire it up
Enable API access
Turn on API access in the client workspace and generate the public and secret keys you need for delivery and sync.
Set allowed domains
Add the frontend domains that are allowed to call the API. Browser requests and Postman flows are checked against the allowed-domain rules.
Use the public key for delivery
All public delivery requests use `X-Public-Key`. Only private sync endpoints also require `X-Secret-Key`.
Read structured content
Use the content endpoints for pages, products, blogs, services, projects, FAQs, teams, pricing, and marketing sections.
Handle home-page custom HTML
Use the home builder settings returned by the API when your theme/runtime supports admin-defined HTML blocks after selected home positions.
Apply scoped layout controls
Home and each dynamic page can carry independent sort, column, row, and item-count controls for reusable sections. Do not reuse home layout values for dynamic pages.
Respect custom HTML placement blocks
Dynamic page responses can include `customHtmlSectionsJson` and parsed `customHtmlSections` so finalized runtimes can inject admin-defined HTML immediately after the chosen page or module position.
Render custom section tokens in runtime
Custom sections currently render through `[[dynamic-section slug="..." limit="6" style="service-card"]]` tokens stored inside custom HTML. They are runtime features today, not separate delivery endpoints.
Respect storefront runtime boundaries
Cart, checkout, order success, invoices, returns, wishlist, and currency switching are hosted storefront routes, not `/api/v1` delivery endpoints.
Use symbol-first formatted prices in uploaded themes
Uploaded theme context includes `currency`, `currencies`, and formatted product/pricing-plan prices so designers should render `*_formatted` values before raw numeric values.
Use direct pricing-plan checkout
Pricing-plan cards should link to `plan.checkout_url` so users move directly into checkout; checkout creates the internal plan cart line with no product variant.
Send leads and form data back
POST to the form submission or widget lead endpoints so the CMS stays the system of record for captured business enquiries.
Sync leads into ERP
Use `/api/v1/forms/{formId}/submissions` for form-specific lead sync from an approved ERP domain. If the domain is not allowed, the API returns `Domain is not allowed.`
Endpoint group
Core delivery
These endpoints power standalone frontends, dynamic websites, and headless delivery flows for LaysanX Web.
Feature
Method
Path
Notes
/api/v1/site/config
Returns theme, settings, menus, topbar, footer, home settings, scoped section controls, and SEO structure.
/api/v1/site/routes
Returns canonical routes plus generated content routes for static generation and crawl planning.
/api/v1/site/engagement
Returns popup, widget, and reusable engagement payloads.
/api/v1/site/home
Returns the home composition including sliders, products, projects, blogs, galleries, FAQs, home-scoped section layout controls, and home custom HTML placement data.
/api/v1/sliders
Fetch active homepage and campaign slider content.
Endpoint group
Pages and services
These endpoints expose CMS-managed pages and service content for dynamic or headless frontends.
Feature
Method
Path
Notes
/api/v1/pages
Returns CMS-managed dynamic pages including parsed custom HTML placement blocks.
/api/v1/pages/{slug}
Returns one page by slug, including `customHtmlSectionsJson`, parsed `customHtmlSections`, and page-scoped layout behavior for theme/runtime placement. Custom section modules are currently injected by runtime tokens rather than a separate delivery endpoint.
/api/v1/pages/{slug}/view
Tracks page view events for a page.
/api/v1/services
Returns published services.
/api/v1/services/{slug}
Returns one service by slug.
/api/v1/services/{slug}/view
Tracks service page views.
Endpoint group
Products, projects, and blogs
These endpoints expose public growth content for product marketing, case studies, and editorial surfaces.
Feature
Method
Path
Notes
/api/v1/products
Returns published product content.
/api/v1/products/{slug}
Returns one public product by slug. Hosted storefront runtime adds variant matrix, gallery/variant image switching, wishlist, cart, and currency-aware pricing behavior.
/api/v1/products/{slug}/view
Tracks product page views and returns assigned form/pricing-plan/custom-field/multi-feature payloads for detail runtimes.
/api/v1/products/{slug}/variants
Returns active variants with SKU, attributes, pricing, stock, and variant image payloads for product-detail selectors.
/api/v1/projects
Returns published projects or case studies.
/api/v1/projects/{slug}
Returns one project by slug.
/api/v1/projects/{slug}/view
Tracks project page views.
/api/v1/blogs
Returns published blogs.
/api/v1/blogs/{slug}
Returns one blog by slug.
/api/v1/blogs/{slug}/view
Tracks blog page views.
Endpoint group
Jobs, news, events, and notifications
These endpoints cover list/detail/view flows for time-based or communication-driven public content types.
Feature
Method
Path
Notes
/api/v1/jobs
Returns published jobs.
/api/v1/jobs/{slug}
Returns one job by slug.
/api/v1/jobs/{slug}/view
Tracks job page views.
/api/v1/news
Returns published news items.
/api/v1/news/{id}
Returns one news item by numeric id.
/api/v1/news/{id}/view
Tracks news page views.
/api/v1/events
Returns published events.
/api/v1/events/{id}
Returns one event by numeric id.
/api/v1/events/{id}/view
Tracks event page views.
/api/v1/notifications
Returns published notifications.
/api/v1/notifications/{id}
Returns one notification by numeric id.
/api/v1/notifications/{id}/view
Tracks notification opens and views.
Endpoint group
Supporting website modules
These endpoints return supporting website data used across dynamic websites, headless themes, and landing pages.
Feature
Method
Path
Notes
/api/v1/gallery
Returns media and gallery assets for frontend rendering.
/api/v1/faqs
Returns published FAQ content.
/api/v1/teams
Returns team and people content.
/api/v1/pricing-plans
Returns public pricing-plan summaries with direct checkout URLs and null variant identifiers for plan checkout.
/api/v1/pricing-plans/{id}
Returns one pricing plan and its detail rows.
/api/v1/commerce/currencies
Returns active currencies with symbol, conversion rate, and default flag for symbol-first storefront pricing and selected-currency payment handoff.
/api/v1/forms
Returns published forms.
/api/v1/forms/{id}
Returns one form and its public-field definitions.
/api/v1/marketing-sections
Returns reusable marketing section payloads.
/api/v1/auxiliary-sections
Returns secondary sections used across layouts and pages.
Endpoint group
Submissions, sync, and runtime relay
These endpoints support lead capture, form storage, CRM-style sync workflows, and standalone runtime relays.
Feature
Method
Path
Notes
/api/v1/forms/{id}/submissions
Creates a form submission from a standalone frontend, public website, or widget.
/api/v1/form-submissions
Private sync endpoint requiring both public and secret keys.
/api/v1/forms/{formId}/submissions
Private ERP/CRM endpoint for one form. Requires public key, secret key, and an allowed Origin/Referer domain.
/api/v1/form-submissions/{id}
Private sync endpoint requiring both public and secret keys.
/api/forms/submit
Used by standalone theme runtimes to forward submissions into the main API.
Endpoint group
Commerce operations
Private commerce endpoints for ERP/admin integrations. These require both public and secret API keys.
Feature
Method
Path
Notes
/api/v1/orders/{orderNumber}
Returns the main order, linked sub-orders, line items, status fields, and invoice summary.
/api/v1/orders/{orderNumber}/invoice
Returns invoice data and the printable storefront invoice route.
/api/v1/orders/{orderId}/status
Updates order, payment, and fulfillment status for one main order or sub-order independently.
/api/v1/returns
Lists return/refund requests, optionally filtered by status.
/api/v1/returns/{requestNumber}
Returns one return request by request number.
/api/v1/returns/{id}/status
Approves or rejects a return and updates refund amount/status plus admin remarks.
/api/v1/support-tickets/{ticketNumber}
Returns ticket status and optional messages for private support integrations.
Endpoint group
Chat widget
These endpoints power the knowledge-base widget, question answering, lead capture, and intent-gated order/ticket status workflows.
Feature
Method
Path
Notes
/widget/bootstrap
Returns widget configuration and public runtime payload.
/widget/ask
Submits a knowledge-base backed user question. Also handles internal order status and support ticket status only when the message clearly asks for status or includes IDs such as ORD-* / LX-TKT-*.
/widget/lead
Creates a lead from the widget flow.
Endpoint group
Storefront runtime routes
These are hosted runtime pages rather than public `/api/v1` endpoints, but they are part of the current release contract for QA and theme teams.
Feature
Method
Path
Notes
/cart
Cart, quantity, coupon, pricing summary, and selected currency.
/checkout
Guest/customer checkout, pricing-plan direct checkout, gateway selection, selected-currency payment handoff, and order creation.
/order-success
Designed success page after checkout. Cart should be cleared after order placement.
/orders, /invoice
Customer/admin invoice access and order/sub-order status visibility.
/returns
Return request flow with status, rejection remarks, and refund pending/paid state.
/currency
Stores selected currency, converts active cart, and returns safely to the current page.
/customer/wishlist
Customer wishlist add/remove behavior used by product detail/listing actions.
Examples
Copy-ready implementation examples.
Use these snippets to get delivery, forms, widgets, and sync flows working quickly.
cURL
Authenticate a delivery request
curl --request GET "https://cms.yourdomain.com/api/v1/site/config" \
--header "X-Public-Key: pk_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" \
--header "Origin: https://www.yourfrontenddomain.com"
JavaScript
Fetch a dynamic page in JavaScript
const response = await fetch("https://cms.yourdomain.com/api/v1/pages/about-us", {
headers: {
"X-Public-Key": "pk_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
"Origin": "https://www.yourfrontenddomain.com"
}
});
if (!response.ok) {
throw new Error("Unable to load page content");
}
const page = await response.json();
console.log(page.title, page.bodyHtml);
JavaScript
Submit a form from a standalone frontend
await fetch("https://cms.yourdomain.com/api/v1/forms/12/submissions", {
method: "POST",
headers: {
"Content-Type": "application/json",
"X-Public-Key": "pk_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
"Origin": "https://www.yourfrontenddomain.com"
},
body: JSON.stringify({
pageName: "/contact",
country: "India",
city: "Gurugram",
formData: {
"Your name": "Priya Sharma",
"Your Email": "priya@example.com",
"Your Mobile Number": "+91-9876543210",
"Message": "I want a walkthrough for LaysanX Web."
}
})
});
JavaScript
Bootstrap the chat widget
const widget = await fetch("https://cms.yourdomain.com/widget/bootstrap?clientId=1001&widgetKey=kb_xxxxx&domain=www.yourfrontenddomain.com", {
headers: {
"Origin": "https://www.yourfrontenddomain.com"
}
}).then((response) => response.json());
console.log(widget.siteName, widget.theme, widget.welcomeMessage);
cURL
Submit through the standalone runtime relay
curl --request POST "https://standalone.yourdomain.com/api/forms/submit" \
--form "formId=12" \
--form "pageName=/contact" \
--form "Your name=Priya Sharma" \
--form "Your Email=priya@example.com" \
--form "Your Mobile Number=+91-9876543210"
cURL
Read submissions in a private sync process
curl --request GET "https://cms.yourdomain.com/api/v1/form-submissions" \
--header "X-Public-Key: pk_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" \
--header "X-Secret-Key: sk_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" \
--header "Origin: https://www.yourfrontenddomain.com"
JavaScript
Read one form's leads from an ERP domain
const response = await fetch("https://cms.yourdomain.com/api/v1/forms/12/submissions?page=1&pageSize=50", {
headers: {
"X-Public-Key": "pk_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
"X-Secret-Key": "sk_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
}
});
if (!response.ok) {
const error = await response.json();
throw new Error(error.error || "Unable to load leads");
}
const leads = await response.json();
console.log(leads.pagination, leads.items);
Go-live checklist
Final checks before you put this in front of customers.
These are the practical release checks we recommend before handing the stack to frontend, QA, or production operations teams.
Production readiness
Validate API keys and allowed domains
Confirm the public key works for `/api/v1/site/config`, the secret key works for `/api/v1/form-submissions`, `/api/v1/forms/{formId}/submissions`, and every live frontend or ERP domain is allowed.
Test widget runtime on real domains
Verify `/widget/bootstrap`, `/widget/ask`, and `/widget/lead` using the production widget key and real website hostnames.
Test widget status lookups
Ask a normal greeting, an order status question with `ORD-*`, and a ticket status question with `LX-TKT-*` to confirm conversation is not hijacked by status lookup.
Check form submission flows
Run both JSON and multipart submissions for at least one production form, then confirm the lead appears in Client Admin.
Check storefront commerce
Place a multi-product order, confirm main/sub-orders and separate invoices, verify cart clears, order-success opens, and admin can edit connected orders independently.
Check currency and pricing plan checkout
Switch currency from the storefront topbar, confirm symbol-first pricing, active cart conversion, payment gateway currency handoff, and pricing-plan direct checkout.
Check product variants and wishlist
Confirm add/edit product variant rows are compact, variant images preload into the gallery, selected variants switch the main image, and wishlist heart actions are visible.
Check returns and refunds
Approve and reject return requests, record rejection remarks, and mark refund state from pending to paid where applicable.
Check AI generated themes
Build an AI website theme ZIP, confirm it preserves the matching sample-project design, and use Add to Themes without triggering create-draft validation.
Check billing, wallet, and AI generation
Confirm token pricing, recharge actions, shared-token usage, image generation, download/delete, and billing ledger pages load without loops.
Check dynamic page and home-page rendering
Verify selected sections, scoped column/row/count controls, custom HTML placements, custom section tokens, item limits, pricing/form split layout, logo/testimonial sliders, and finalized themes render from the current page/home configuration.
Check helpdesk and queued notifications
Open a helpdesk ticket, send replies from both sides, and confirm the queued notification worker keeps email delays from blocking the UI.
Check custom-domain rules
Confirm trial workspaces open on public route only, paid plans can request allowed domain counts, and production domains are mapped through nginx/SSL provisioning.
Check cache refresh after publish
Restart both SaaS and client apps after publish and verify HTML/static responses revalidate instead of serving stale CSS, JavaScript, or layout output.
Confirm routes, robots, and sitemap
Open the client and SaaS `sitemap.xml`, `robots.txt`, and route-discovery responses so SEO and crawl surfaces are not left blank.
Keep docs and Postman in sync
Ship the Postman collection together with the API documentation so implementation teams are not guessing from stale examples.
Use these during launch
Postman collection
Run the same requests that frontend and QA teams will use in production.
Download collection
Markdown docs pack
Share the delivery API, widget API, and feature-coverage docs with implementation partners.
API endpoint index
Jump back to the grouped endpoint coverage for delivery, widget, and sync routes.
View endpoint groups
Product documentation
Review the public product narratives and rollout positioning before launch content goes live.
View product docs
Product documentation
Detailed feature documentation for all product lines.
LaysanX Web handles headless CMS and AI website builder workflows. LaysanX Biz handles business operations and ERP-grade workflow control. LaysanX Eye handles CCTV visibility, playback, and surveillance-led operations.
Headless CMS + AI Website Builder
LaysanX Web
LaysanX Web gives your team one place to manage pages, blogs, forms, APIs, SEO structure, content workflows, and headless delivery without turning every launch into a developer bottleneck.
- Headless CMS and AI website builder workflows in one publishing system.
- Dynamic pages, blogs, forms, FAQs, jobs, events, galleries, and structured website content from one admin layer.
- Headless-friendly delivery APIs for standalone themes, apps, widgets, ERP lead sync, and external frontend stacks.
- AI blog automation, image generation, token wallets, media uploads, helpdesk, and custom-domain workflows for production website operations.
Dynamic content engine
Pages, blogs, categories, SEO metadata, structured publishing, and content operations for fast launches.
Headless API delivery
Deliver content to external frontends, standalone theme projects, widgets, and custom web experiences.
Lead capture and growth tools
Forms, landing pages, engagement flows, blog publishing, and conversion-ready public website tooling.
Dynamic pages
Create, manage, and publish flexible pages for campaigns, brands, products, and corporate content.
Blog publishing
Run editorial calendars, product updates, AI-assisted content, and SEO articles from one system.
Form builder
Capture leads, enquiries, and internal requests with structured forms and response workflows.
FAQ management
Organize reusable question-and-answer content for support, sales, and public knowledge surfaces.
Jobs and careers
Publish hiring pages, job listings, and recruiting content directly from the CMS.
Events and launches
Manage event pages, launch campaigns, schedules, and promotional content blocks.
Services showcase
Present service lines, delivery packages, and category-led offerings cleanly.
Products catalog
Manage product records, descriptions, pricing contexts, and structured product content.
Projects and case studies
Show portfolio, implementation stories, and client proof with reusable content structures.
Media and galleries
Support visual publishing, reference assets, and website-ready media organization.
SEO metadata control
Manage titles, descriptions, slugs, canonical structure, and search-ready content operations.
Theme-ready publishing
Connect the CMS to standalone theme projects and runtime-ready frontend delivery.
API access
Expose content to external frontends, apps, and integrated website experiences through delivery APIs.
Allowed-domain API security
Protect public delivery and private ERP/CRM sync calls with allowed-domain checks and scoped API keys.
ERP lead sync
Read form submissions by form ID for CRM, ERP, and client-side reporting tools from approved domains.
Content categories
Keep content organized with categories, groupings, and reusable structures for scale.
AI blog workflows
Generate draft content, trend-aware topics, headline scoring, social captions, and supporting metadata with AI assistance.
AI image generator
Create branded visuals or vendor AI images with wallet/shared-token charging, gallery history, JPG download, and delete controls.
Media library uploads
Upload reusable client assets with plan-aware file size checks and safer file validation rules.
Custom section module
Build reusable section collections with fields, items, file uploads, and optional detail pages, then inject them into home or dynamic pages with `[[dynamic-section ...]]` tokens.
Home and dynamic page custom HTML
Place admin-defined HTML blocks after selected home-page or dynamic-page positions to ship campaign strips, embeds, and custom sections without code edits.
Configurable contact page
Assign any form to the built-in contact page, customize its headings, and override it completely with a dynamic page using the `contact` slug.
Client helpdesk
Let clients raise tickets, continue threaded conversations, and receive LaysanX replies from directly inside the client panel.
Queued notification engine
Lifecycle emails for plans, wallets, referrals, and support are queued in the background so mail-server issues do not hang production actions.
Custom-domain onboarding
Support hosted public routes, paid-plan domain requests, domain counts, and production mapping workflows.
Billing and token wallet
Show plan status, trial-to-paid behavior, token pricing, wallet recharges, and AI usage ledgers.
Public website management
Run the core website, landing pages, CTAs, and information architecture from one place.
Growth operations support
Coordinate content, acquisition, and launch workflows without jumping across scattered tools.
Built for external growth
LaysanX Web is the product you use when growth depends on launching and updating digital experiences quickly. Marketing, SEO, content, partnerships, product launches, and campaign pages can all move from the same control layer without waiting on scattered tools or one-off admin panels.
Headless CMS and website builder in one stack
Some teams want server-rendered websites. Some want a separate frontend theme or app. Some want both. LaysanX Web supports the publishing model you actually need, which makes it a strong fit for agencies, founders, and product teams that expect requirements to evolve.
Ready for content operations
This is not just a brochure page builder. It is designed for repeated publishing, reusable content structures, public forms, blogs, SEO assets, and connected admin workflows that still feel manageable once the website operation gets busy.
Who should use LaysanX Web?
Teams responsible for public growth, websites, content publishing, SEO, forms, and frontend delivery will get the most value from LaysanX Web.
Can LaysanX Web be used headlessly?
Yes. It can power standalone frontends and delivery flows through its API-driven publishing model.
Is it only for blogs and pages?
No. It also covers forms, FAQs, jobs, services, products, projects, SEO control, and wider public content operations.
Can LaysanX Web power a corporate website?
Yes. It is a strong fit for corporate sites, product marketing sites, campaign microsites, and multi-page brand websites.
Can I use LaysanX Web for landing pages and campaigns?
Yes. It is built to support repeated landing page launches, campaign content, product launches, and structured growth publishing.
Does LaysanX Web support forms?
Yes. Form capture is part of the publishing surface, so you can manage public enquiries, demo requests, and lead capture flows.
Can I manage SEO metadata page by page?
Yes. The platform supports SEO title, description, slug, and structured publishing controls across content surfaces.
Does it support product pages?
Yes. Product catalog content is part of the public website feature surface.
Can I publish blogs regularly from it?
Yes. Blog publishing, AI-assisted blog workflows, and editorial operations are part of the product.
Does it support FAQs and support content?
Yes. FAQ management is included so public support content can stay organized and reusable.
Can agencies use LaysanX Web for clients?
Yes. Agencies and implementation teams can use it to manage content-heavy public website operations more cleanly.
Can it connect to a custom frontend?
Yes. The headless delivery API is designed for custom websites, standalone themes, and external frontend stacks.
Can we use it without going fully headless?
Yes. You can use it as a dynamic CMS, a headless CMS, or a hybrid model depending on your rollout.
Does it include media and gallery management?
Yes. It includes media and gallery-friendly publishing for visual content surfaces.
Can LaysanX Web manage careers and job listings?
Yes. Job and careers content can be published directly from the CMS.
Can we manage services and case studies too?
Yes. Services, projects, and case-study content are part of the content model.
Is it useful for content marketing teams?
Yes. Teams doing frequent publishing, landing pages, and SEO content work will find it especially useful.
Can it help reduce developer bottlenecks?
Yes. It gives non-developer teams more direct operational control over website publishing workflows.
Is API access included?
Yes. API access is part of the LaysanX Web product direction for delivery, integrations, and standalone frontends.
Can LaysanX Web work with your chat widget and AI features?
Yes. It fits naturally with the LaysanX knowledge-base widget, AI blog generation, and website-side growth tooling.
How fast can a team start using LaysanX Web?
Once the workspace is ready, teams can start setting up pages, content structures, forms, and publishing surfaces quickly.
Is LaysanX Web meant for long-term content operations?
Yes. It is designed for repeated publishing and operational stability, not just one-time website setup.
Business Operations Software + ERP
LaysanX Biz
LaysanX Biz is built for teams that need stronger internal operations: accounting, HRMS, inventory, workflows, approvals, and operational visibility without stitching together spreadsheets and disconnected dashboards.
- Business operations software for accounting, HRMS, inventory, approvals, and admin control in one product surface.
- Built for internal operational discipline instead of marketing-only workflows.
- Strong fit for businesses that want fewer disconnected back-office systems.
Accounting control
Track financial operations, ledgers, billing flows, and accounting visibility inside a structured operational surface.
HRMS workflows
Manage employees, structure, attendance-adjacent processes, and internal operational accountability.
Inventory and business ops
Stay on top of items, movement, stock control, and operational workflows that need real process visibility.
Purchase workflow
Support procurement, inward processes, and structured business purchasing control.
Sales operations
Coordinate sales-side operational records, commercial flow, and internal execution visibility.
Ledger visibility
Track account movement, entries, and finance-side operational reference points.
Expense tracking
Bring recurring and operational expense activity into a controlled business system.
Team structure
Map roles, departments, and internal people structure with cleaner visibility.
Employee records
Maintain employee profiles, assignment information, and internal workforce references.
Approval workflows
Move operational decisions through clearer approval checkpoints instead of message chaos.
Inventory movement
Monitor stock flow, adjustments, transfers, and item-level operational changes.
Stock visibility
See what is available, moving, pending, or getting tight before it becomes a fire drill.
Vendor coordination
Keep supplier-side operational relationships more organized and easier to follow.
Operational dashboards
Give managers and owners one place to read the state of internal execution.
Document references
Attach the business context and operational paperwork teams need to act with confidence.
Internal controls
Reduce spreadsheet sprawl by giving structured internal work a real system home.
Cross-team visibility
Connect finance, HR, stock, and admin work without losing accountability.
Process standardization
Turn repeated operational work into more consistent and trackable workflows.
Management reporting
Support leadership review with cleaner operational summaries and business status visibility.
Separate accounting path
Pair LaysanX Biz with dedicated accounting software when deeper finance specialization is needed.
For internal operations, not external marketing
LaysanX Biz is for the work that happens after leads arrive and the company actually needs to run. That means operational accuracy, responsibility, approvals, and visibility across teams.
Business operations software without tool sprawl
Businesses often end up with separate systems for accounting, HR, approvals, inventory, and internal reporting. LaysanX Biz is designed to reduce that sprawl and make the operational picture easier to understand.
Separate accounting software also available
For teams that need dedicated accounting depth or a separate deployment path, we also offer accounting software as an additional software line alongside the LaysanX product family.
Who should use LaysanX Biz?
Operations, finance, HR, admin, and leadership teams that need stronger internal process control are the main fit.
Does LaysanX Biz include accounting workflows?
Yes. Accounting is one of its major pillars, alongside HRMS, inventory, and operational visibility.
Do you also offer separate accounting software?
Yes. We also provide a separate accounting software path for teams that need deeper dedicated finance specialization.
Is LaysanX Biz only for very large companies?
No. It is useful for any business that needs stronger internal coordination across finance, people, stock, and admin workflows.
What kind of internal operations does it cover?
It covers accounting-facing work, HRMS, inventory, approvals, reporting, vendor coordination, and structured internal execution.
Can it replace spreadsheets for internal ops?
That is one of the goals. It gives repeated internal workflows a system home instead of relying on scattered spreadsheet chains.
Does it support approval workflows?
Yes. Approval flow and operational checkpoint visibility are part of the product direction.
Can HR teams use it for employee records?
Yes. Employee information and people-structure visibility are included in the HRMS side.
Is inventory part of the product?
Yes. Inventory visibility and movement tracking are key parts of LaysanX Biz.
Can finance teams use it for ledgers and expenses?
Yes. Ledger visibility and expense-related operational control are included.
Is it useful for admin-heavy businesses?
Yes. Businesses with internal coordination, paperwork, approvals, and multi-step execution are a strong fit.
Can management get dashboards from it?
Yes. Operational dashboards and reporting visibility are part of the internal-control surface.
Can it support vendor and purchase workflows?
Yes. Vendor coordination and purchase workflows are part of the broader business operations model.
Is it meant to reduce disconnected back-office tools?
Yes. That is one of the central reasons LaysanX Biz exists.
Can teams use LaysanX Biz without LaysanX Web?
Yes. The two products are separate lanes, so a business can start with only the internal operations side.
Can a company use both Web and Biz together?
Yes. Many businesses will want public growth systems on one side and internal operations control on the other.
Does LaysanX Biz help with cross-team visibility?
Yes. It is designed to make finance, HR, stock, and operations easier to understand in one place.
Is it a generic ERP clone?
No. The goal is a practical operating system for real business execution, not just a bloated checkbox ERP.
Can it fit growing mid-sized companies?
Yes. It is especially useful when a company is growing out of informal internal systems.
Can we start small and expand later?
Yes. Teams can begin with the most important operational workflows and grow deeper over time.
How does the separate accounting software fit in?
If a business wants deeper dedicated finance specialization, the separate accounting software can sit alongside LaysanX Biz.
What is the biggest advantage of LaysanX Biz?
It gives internal operations a clearer shared system, which reduces confusion, delays, and scattered back-office work.
CCTV operations and monitoring software
LaysanX Eye
LaysanX Eye helps teams watch live feeds, review playback, receive alerts, track branch activity, and turn CCTV footage into a more useful operational system instead of a passive recorder screen.
- Monitor multiple branches and camera feeds from one centralized software surface.
- Use live view, playback, snapshots, and event review without staying tied to a single DVR screen.
- Layer operational use cases like branch supervision, missed-event review, guard tracking, and AI alerts on top of CCTV infrastructure.
Central live view
Watch live camera streams from one software surface instead of jumping between scattered DVR or NVR windows.
Playback and review
Open recorded footage quickly to investigate incidents, verify events, and review what happened at a branch or camera.
Multi-camera wall
View multiple cameras on one screen to monitor counters, entrances, warehouses, offices, and field points together.
Remote monitoring
Access camera visibility from anywhere so owners, managers, and operations teams stay informed off-site too.
Snapshot capture
Save still frames from important moments for escalation, reporting, and operational evidence.
Clip download
Download important footage clips for incident handling, audit records, or sharing with authorized teams.
Camera health alerts
Get notified when cameras disconnect, storage fails, or feeds go offline so blind spots do not stay hidden.
Hard disk failure visibility
Track recorder health and storage issues before footage loss becomes an operational problem.
AI motion alerts
Surface important movement-based events so teams can focus on what changed instead of watching every minute manually.
Intrusion events
Flag after-hours entries, restricted-zone movement, or perimeter-style camera events for quicker action.
Missed visitor review
Identify missed visitors or unattended entry points so front-desk and branch teams can improve responsiveness.
Multi-branch dashboard
Bring all branches into one overview so central teams can compare activity, health, and camera coverage quickly.
Retail and office oversight
Use CCTV software not only for security, but also for counters, store floors, office discipline, and site operations.
Warehouse visibility
Monitor dispatch zones, material movement, loading points, and stock-sensitive areas from one operational layer.
Security team coordination
Help guards, supervisors, and central review teams work from the same event and footage context.
Patrolling accountability
Use footage and event visibility to verify site rounds, coverage, and on-ground security discipline.
User access control
Give branches, managers, and central teams the right footage visibility without sharing everything to everyone.
Smart notifications
Push relevant alerts to operators so they can react faster to feed loss, motion, intrusion, or incident patterns.
Operational incident review
Use recorded events to investigate disputes, missing stock, queue issues, delivery problems, or access anomalies.
Business CCTV intelligence
Turn surveillance into a business operations tool for oversight, compliance, discipline, and accountability.
Built for active monitoring, not passive recording
Many CCTV setups only become useful after a problem happens. LaysanX Eye is designed to make cameras more useful before, during, and after events by helping teams watch live, review incidents faster, and stay aware of feed health across locations.
Useful for branches, stores, offices, and warehouses
The product is shaped around real multi-site operations. That means branch visibility, supervisor oversight, visitor review, stock-area monitoring, dispatch checks, and operational camera workflows that help business teams, not just pure security teams.
AI and alert-first surveillance workflow
When motion events, intrusion patterns, or feed failures happen, the right people should know quickly. LaysanX Eye supports a more alert-driven model so teams spend less time manually checking every screen and more time acting on real signals.
What is LaysanX Eye?
LaysanX Eye is CCTV monitoring and surveillance operations software for live view, playback, alerts, and centralized camera visibility.
Who should use LaysanX Eye?
Retail chains, offices, warehouses, branches, security teams, and operations managers who need better camera visibility are a strong fit.
Can it monitor multiple branches?
Yes. Multi-branch and multi-location visibility is one of the main product use cases.
Can I watch live camera feeds remotely?
Yes. LaysanX Eye is designed to help authorized users access live visibility away from the physical recorder location.
Does it support playback?
Yes. Playback and recorded footage review are core parts of the product.
Can I download footage clips?
Yes. Teams can download relevant clips for review, evidence, escalation, or reporting.
Can I capture screenshots from footage?
Yes. Snapshot capture is part of the review workflow.
Does it show multiple cameras on one screen?
Yes. Multi-camera wall style visibility is part of the product direction.
Can it alert us when a camera goes offline?
Yes. Camera disconnection and feed-health alerting are included in the feature model.
Does it help with recorder or hard-disk failures?
Yes. Recorder and storage-health visibility are covered so teams know when recording infrastructure needs attention.
Is AI alerting part of the product?
Yes. LaysanX Eye is positioned to support AI motion, intrusion, and event-led alert workflows.
Can it help with visitor or entry-point review?
Yes. It can support use cases like missed visitor checks and front-entry incident review.
Is it only for security teams?
No. Branch managers, retail operators, warehouse supervisors, and business owners can all use it.
Can CCTV be used for operational oversight too?
Yes. Many customers use camera visibility for execution checks, queue review, dispatch oversight, stock movement visibility, and discipline-related monitoring.
Can different teams get different access?
Yes. The product supports the idea of controlled visibility by role or responsibility.
Can LaysanX Eye work alongside the other LaysanX products?
Yes. It sits naturally beside LaysanX Web for public growth systems and LaysanX Biz for internal operations.
Does it fit warehouses and stock-heavy businesses?
Yes. Warehouses, loading points, dispatch areas, and stock-sensitive spaces are strong use cases.
Can it help central teams supervise branches?
Yes. Central monitoring and cross-branch visibility are key benefits.
Is it useful for guard accountability and patrolling review?
Yes. Security management and patrol verification are part of the broader operational fit.
Can the software reduce blind CCTV operations?
Yes. Feed-health alerts, centralized dashboards, and event review help reduce the risk of unnoticed failures.
How is LaysanX Eye different from a basic DVR screen?
It adds a centralized software layer for branch monitoring, alerts, playback workflows, and business-side CCTV visibility.
Can businesses start with a smaller deployment and expand later?
Yes. Teams can start with the most important cameras or sites and grow the rollout over time.
Need implementation help?
Use the docs for delivery, then talk to us for rollout support.
We can help your team launch LaysanX Web, operationalize LaysanX Biz, deploy LaysanX Eye, or wire the APIs into your standalone frontend stack.