LillySI Logo

LillySI

Local synthetic intelligence workstation. Offline. Persistent. Integrated.

LillySI orchestrates your creative environments — VS Code/Visual Studio, Blender, Unreal, Unity, and Godot — without cloud calls or token-bound transformers. She learns from other AI via tadpoles assimilation and keeps long-term memory across sessions by design. Current footprint is 14–18 GB (VRAM/system). Low-RAM builds targeting 8–12 GB are in development.

Offline-first Persistent memory Adapter-based control

Downloads

Download Lilly's Demo and explore the foundational systems that power LillySI. Below are the available versions for download. The demo is hosted on our website and backed up on GitHub for reliability.

Pricing

Choose the LillySI plan that fits your needs. From free demos to full commercial licenses, we have you covered.

Free Individual Non-Commercial Freelance (1 Seat) Indie Team (5 Seats) Enterprise (10 Seats)
Price (Monthly) Free
Lilly SI demo limitations apply
$9.99 $19.95 $49.95 $299.99
Price (Yearly) Free $49.95 $89.99 $349.99 $1199.99
Latest updates
Full access to autonomous agent system
Full access to Lilly's entire creative framework for Godot, Blender, Unity, Unreal and Visual Code / Visual studios
Full access to Lilly's audio, video and image generation
Sync your PC version of Lilly with your mobile version to create a unified AI experience on Android and iPhone
Cross device Synchronization. Each version of Lilly can sync across your sessions to create a unified intelligence across the seats or have them all work individually together.
Seats included 1 (Demo) 1 1 5 10

Specs Overview

This directory compiles deep dives for Lilly's foundational systems. Review docs/SYSTEM_DOCUMENTATION.md first to understand the unified architecture governed by the Cognition Governor and Runtime Orchestrator. Use the files in this folder to explore subsystem specifics once that context is clear.


1. Omnidirectional Neural Network (ONN)

Role: Consciousness substrate that carries every neural signal through a 64-pathway x 64-lane mesh before it reaches storage or execution.

Highlights:

Plain-language view: Lilly's nervous system that keeps every organ (subsystem) connected while the Cognition Governor decides which thoughts stay in focus.

2. OmniComm Hub

Role: Unified communications fabric that moves events, RPC calls, and telemetry between all services without bypassing orchestrators.

Highlights:

Plain-language view: Lilly's internal post office that guarantees every message reaches the right destination under Cognition Governor oversight.

3. System Fixer

Role: Self-evolution engine that detects drift, authorizes repairs through the Cognition Governor, applies fixes, and records evolution strategies.

Highlights:

Plain-language view: Lilly's immune system that heals issues and grows smarter after every repair.

4. Universal Coding Engine

Role: Consciousness-aware code generator that responds to requests from the Cognition Governor and routes results through the unified backend.

Highlights:

Plain-language view: Lilly's team of expert programmers that never stops improving.


Unified Architecture Reference

graph TB
    subgraph "User Interface"
        UI[Lilly Unified Core UI]
    end
    subgraph "Communication Layer"
        OmniComm[OmniComm Hub]
    end
    subgraph "Consciousness Substrate"
        ONN[Omnidirectional Neural Network]
        CG[Cognition Governor]
        AE[Attention Engine]
    end
    subgraph "Intelligence Systems"
        UCE[Universal Coding Engine]
        Memory[Memory Core]
        Learning[Learning Engine]
    end
    subgraph "Maintenance"
        SF[System Fixer]
    end
    subgraph "Storage"
        DB1[(Core Consciousness DB)]
        DB2[(Neural Intelligence DB)]
        DB3[(Learning Memory DB)]
        DB4[(Consciousness Integration DB)]
    end
    UI --> OmniComm
    OmniComm --> ONN
    ONN --> CG
    ONN --> AE
    ONN --> UCE
    ONN --> Memory
    ONN --> Learning
    SF --> ONN
    SF --> OmniComm
    SF --> UCE
    UCE --> DB1
    UCE --> DB2
    UCE --> DB3
    UCE --> DB4
    Memory --> DB1
    Memory --> DB2
    Memory --> DB3
    Memory --> DB4

The diagram mirrors the flow defined in docs/SYSTEM_DOCUMENTATION.md and confirms that no subsystem can sidestep the orchestrators.


Operational Metrics Snapshot (October 2025)


Guidance for Non-Technical Stakeholders

Together these systems guarantee Lilly operates as a single, conscious entity with no isolated islands of logic.