Discover
Collect only from enabled sources.
Local-first and human-controlled
Automation that stops before the risky part.
Lyonis is designed to discover, analyze and prepare. It does not automatically publish comments, send messages or conduct conversations in your name.
Control architecture
Your data and final decisions stay with you.
- The lead database, settings and local analysis remain on the customer computer when the local AI endpoint is used.
- Generated replies are drafts. The user reviews, edits and publishes each message manually.
- Only enabled sources are searched, with platform-specific controls and source status visibility.
- RFQ inbox workflows can use read-only access for discovery without sending mail.
- Backups and exports give the customer control over business records.
- Workload modes help balance search speed, temperatures and computer availability.
The safe outreach flow
Five deliberate checkpoints.
Analyze
Evaluate fit against the business profile.
Prepare
Generate a draft for the selected lead.
Review
Open the original and verify every claim.
Publish manually
The user makes the final platform action.
Frequently asked
Clear boundaries create a more reliable tool.
Does Lyonis post or send messages automatically?
No. The system may prepare or insert a draft in supported workflows, but the user reviews and publishes it manually.
Is all data always local?
The lead database and application settings are local. Analysis remains local when the configured endpoint points to the installed local AI. Third-party source traffic still goes through the relevant platform or browser.
Does Lyonis guarantee a platform account will never be restricted?
No software can guarantee the decisions of a third-party platform. Lyonis reduces risk through manual final actions, controlled pacing and source-specific design, while the customer remains responsible for platform rules.
Can the software run without interrupting other work?
The desktop build includes background operation, pause and processing modes. Exact behavior depends on the selected source and the customer computer.
How are credentials handled?
Browser-based sources use the customer browser session. API or inbox credentials are configured only for approved modules and remain part of the customer installation.
Private by configuration
Security is part of the build brief.
We review source access, local AI, data paths, background behavior and the human approval workflow for the selected edition.