For product builders
Package a web app with its DLLs, data files, certificate settings, and service configuration so it can run on your server or a customer machine.
Official Laptika Platform
A local-first .NET platform that turns web projects into installable products. Your interface stays simple, while server-side code, database rules, API logic, AI tools, certificates, licensing, and protection can live behind DLL commands.
Why It Exists
Laptika is for developers and product makers who want the speed of HTML interfaces without losing control of their server logic, data, licensing, and distribution. It gives each feature a place: public UI in static files, trusted behavior in .NET code, durable data in Laptika DB or SQL Server, and product knowledge in a guide that people and AI tools can read.
Package a web app with its DLLs, data files, certificate settings, and service configuration so it can run on your server or a customer machine.
Use C#, VB, and .NET Framework libraries for dynamic server behavior instead of moving valuable rules into browser JavaScript.
Use the reference files and structured JSON to teach an AI what Laptika is, what each product does, and which product should be used for a task.
How Laptika Works
Laptika Server hosts static pages, runs server-side C# or VB code files, and exposes selected public static functions from attached .NET Framework DLLs. Products can store data in Laptika DB, talk to SQL Server, generate sites, answer with AI, or protect .NET output without putting secrets in the browser.
HTML, CSS, and JavaScript load fast from the Laptika web root.
Write server-side C# or VB code files and let Laptika read them like a server language, instead of needing PHP.
The browser calls a named extension route, such as `LaptikaOfficialSite.Commands.ListProducts()`.
The client receives only a response object, not database files, connection strings, product rules, or source code.
Commercial Web Products
A normal website can be copied. A Laptika web product can be installed, configured, licensed, protected, and sold. The public files are only the interface; the valuable code can be locked behind compiled DLLs and protected .NET output.
Move business rules, database calls, calculations, validation, and license checks into DLL commands instead of exposing them in JavaScript.
Ship the site, DLLs, database files, certificates, and service settings as one product that runs locally or on a customer server.
Laptika can read server-side C# and VB code files, so .NET developers can build dynamic web behavior with familiar language and libraries.
Build separate DLL products for API missions, data entry sites, AI features, reports, licensing, or customer-specific integrations.
Product Registry
These records come from the official product database. Add the next product once, and the public site plus AI guide update from the same source.
Product Workflow
Create the new project, usually .NET Framework 4.5 / VS2015 compatible.
Use Laptika DB when a product needs local persistent data.
Add clear DLL commands, or C#/VB server-side files, with mappings for request body, client IP, and method.
Add the DLL to Laptika Server and register product facts in the private product registry.
Write the AI guide field so any future AI knows what the product is and how to use it.
Data Side Demo
The demo accepts suspicious input, but the browser never receives database logic. The request goes to the official site DLL, which classifies the attempt and stores it as data.
{ "decision": "waiting" }
For People And AI
Use this page, the Markdown reference, or the structured JSON guide as the source of truth for Laptika products. Public references explain capabilities and rules without exposing private server paths.
llms.txtShort canonical map for AI tools that need to discover the official Laptika reference quickly.
laptika-reference.mdHuman-readable product guide, architecture notes, workflow, routing model, and product selection rules.
GetAiGuide()Structured JSON from the Laptika DLL, updated from the same product registry used by this page.
Official structured reference will appear here.