Adil model family orbit Three concentric orbits around a local core, inside a dashed permission boundary. Adil Eco on the inner orbit is in release qualification. Adil Core on the middle orbit is in development. Adil Boost on the outer orbit is in development. Permission boundary Eco · In release qualification Core · In development Boost · In development Local core
EPOCH 2.08LOSS 0.290NEURAL EXECUTION
LOCAL ENGINE / 001
RAM 50%
RESOURCE ALLOCATION
LATENCY 24 msCPU 32%ON-DEVICE EXECUTION
THROUGHPUT 42 t/sEXECUTION 0.84 s
Illustrative simulation · demo telemetry

01 ADIL EDGE · LIVING INTELLIGENCE

LOCAL EXECUTION. LIMITLESS POSSIBILITY.

Intelligence,
closer to you.

Local-first AI for applications, devices and developer-controlled workflows.

Supported Platforms & Languages

Development targets · platform qualification pending · SDK unreleased

02 Model families

Three sizes. One family.

Choose the size, then choose where it runs. Each model shows only what has been measured, with its status beside it.

  • Adil Eco

    In release qualification

    867 MBprocess footprint · one Apple M1 · 4K context

    Model file: 484 MB on disk (Q4_K_M).

    The compact model for local execution, structured tasks and developer-controlled actions on everyday CPUs.

    Adil Eco details

  • Adil Core 2B

    In development

    2.12 GBpeak process RAM · preliminary · remote CPU host

    Model file size not published.

    The mid-size family member for personal AI, being measured and shaped. Every figure here is preliminary.

    Adil Core details

  • Adil Boost 4B

    In development

    4.80 GBpeak process RAM · preliminary · remote CPU host

    Model file size not published.

    The largest planned family member, aimed at personal and business workflows. Every figure here is preliminary.

    Adil Boost details

Status is shown on each card. Figures are measured on different hardware, so compare them with care.

Release gates remain open. Not available for download.

03 How local intelligence works

The model proposes. Your application decides.

A conceptual sequence for the Thynkr-developed runtime environment. It describes the intended design, not a feature that has passed qualification.

  1. Local request

    Your application sends a request to the local model. Nothing leaves the device unless your code sends it.

  2. Model inference

    The local model reads the request and produces a response or a proposed tool call.

  3. Permission check

    Your host validates every proposal against the permissions and confirmations you configured.

  4. Approved tool action

    Only an approved action runs, in your code, under your control. Anything else is refused.

04 Platforms and languages

Honest about where it runs.

Platforms

  • macOSApple SiliconInitial development target
  • Linuxx86-64Qualification pending
  • Windowsx86-64Qualification pending
  • Androidarm64Qualification pending

Developer languages

  • Pythoncandidate interface, not releasedCandidate · unreleased
  • TypeScript / Node.jscandidate interface, not releasedCandidate · unreleased
  • C / C++candidate interface, not releasedCandidate · unreleased

Platform names are text identifiers, not endorsements. The developer interface is a candidate contract and may change. No SDK package is publicly released.

05 Engineering evidence

Measured, labelled, bounded.

Every figure names what was measured and where. None is a minimum requirement or a performance promise.

Memory use, by model

These figures measure different things. Read the columns before comparing.

ModelModel file on diskRuntime memoryHardwareContextQuantisationStatus
Adil Eco484 MBQ4_K_M867 MBprocess footprintOne Apple M14KNot statedMeasured
Adil Core 2BNot published2.12 GBpeak process RAMRemote CPU host8KQ4Preliminary
Adil Boost 4BNot published4.80 GBpeak process RAMRemote CPU host8KQ4Preliminary
Peak process RAM, remote CPU host, Q4, 8K context — Core and Boost only. Both are preliminary and come from the same host and settings. Adil Eco is not charted because it was measured on different hardware, so the bars are not like-for-like with the Eco row above.
Bar chart: Core 2B 2.12 GB and Boost 4B 4.80 GB peak process RAM, preliminary, remote CPU host. 0 GB1 GB2 GB3 GB4 GB5 GB Core 2BCore 2B: 2.12 GB peak process RAM, remote CPU host, Q4, 8K, preliminary2.12 GBremote CPU host · Q4 · 8K · preliminaryBoost 4BBoost 4B: 4.80 GB peak process RAM, remote CPU host, Q4, 8K, preliminary4.80 GBremote CPU host · Q4 · 8K · preliminary Bar chart: Core 2B 2.12 GB and Boost 4B 4.80 GB peak process RAM, preliminary, remote CPU host. 0 GB1 GB2 GB3 GB4 GB5 GB Core 2BCore 2B: 2.12 GB peak process RAM, remote CPU host, Q4, 8K, preliminary2.12 GBremote CPU host · Q4 · 8K · preliminaryBoost 4BBoost 4B: 4.80 GB peak process RAM, remote CPU host, Q4, 8K, preliminary4.80 GBremote CPU host · Q4 · 8K · preliminary

Peak RSS from getrusage on one host after a 128-token prompt and a 16-token decode. File size is not memory use. Device requirements and limits.

06 Developer experience

Built so the host stays in charge.

A conceptual walkthrough. The SDK is not released, and nothing below is runnable or downloadable.

  • Your applicationOwns the data, the UI and every side effect.
  • Adil SDKCandidate interfaces for C/C++, Python and TypeScript/Node.
  • Thynkr-developed runtime environment and modelRuns on the device.
  • Permission and confirmation policyYour rules decide which proposed tool calls ever run.
// concept only, not runnable API syntax
host.load(approvedRuntime, verifiedModel)
host.configure(context: 4K)
host.registerTools(boundedTools, confirmationPolicy)

reply = host.generate(request)
// the model returns a proposal, never an action
if (policy.approves(reply.toolCall))
    host.run(reply.toolCall)
else host.refuse(reply.toolCall)

Conceptual host flow. Consult the qualified SDK reference once it is published. Tool permissions and security.

07 Release journey

Gates, not dates.

Each step opens only when its evidence is in. We do not publish launch dates.

  1. Candidate frozen

    Eco A3b weights are frozen as the release candidate.

    Complete
  2. Security remediation

    A scoped security remediation has passed independent review. Additional release qualification remains open.

    In progress
  3. Platform qualification

    macOS, Linux, Windows and Android packages are not yet qualified.

    Pending
  4. Developer availability

    No downloads or SDK packages until independent acceptance and final approval.

    Not started
  5. Core and Boost

    Measured and shaped in development. No release dates are published.

    In development

Recent engineering milestones

Release Centre

Newsletter

The next chapter of local AI.

Follow Adil Eco, Core and Boost. Get important engineering milestones, release announcements and developer news.

Subscriptions not open yet

The email newsletter opens after double opt-in, the newsletter privacy notice and email delivery have been verified. This page does not collect email addresses.

  • Eco
  • Core
  • Boost
  • General news

08 Begin

Start with the evidence.

Explore the candidate model, read how the Thynkr-developed runtime environment keeps your application in charge, and follow the release gates as they open.