Ask your 1C database a question — get a ready query
Lensa knows your configuration structure and writes queries for you: no manual table lookup, attributes hunting or syntax mistakes.
Built from scratch: every line of code is original — no third-party templates, nothing borrowed. Made by a developer with 15 years of 1C experience.
I work without knowing the query language — I just ask the AI. Pulled a list of documents with filters that standard 1C tools can't produce.
Solved an optimization task several times faster than usual. The console reads the configuration context itself, the editor is comfortable — nothing gets in the way.
A full-fledged developer tool, not just an AI bundle: installed in a minute, I carry it across databases. Context loads instantly — I don't copy anything into a chat.
I used to go to a programmer for every data pull and wait a day or two. Now I describe it in words — and get the data myself, straight from the database.
On implementation projects every database is unfamiliar. Lensa figures out the configuration in seconds, so I work with the data right away instead of studying metadata.
I support dozens of client databases. A question like “why is the report wrong” used to eat half a day — now I query an unfamiliar database in minutes, no need to study a custom configuration in detail.
Interface
Demos
An AI workspace for long-running tasks: choose an AI model, add web search, run several conversations in parallel, and take the result as code, tables, or files. Context and costs stay visible.
Claude, GPT, Gemini, DeepSeek, Yandex GPT, and other AI models in one workspace.
The AI model researches the web and attaches source cards to its answer.
Automatic and manual compaction preserve meaning; older history remains expandable.
A response keeps running while you switch to another conversation.
Search, tags, and per-chat settings: AI model, system prompt, and temperature.
Code, Markdown, and tables with fullscreen view, copy, and MD, CSV, or JSON export.
Documents, images, and visual generation directly inside the working conversation.
Tokens, cost, speed, latency, and context usage stay visible in place.
We use them ourselves and share with the community — free under MIT.