🍪 We use cookies

    We use cookies to improve your experience on our website, analyse traffic, and for marketing purposes. By clicking "Accept All", you consent to our use of cookies. You can also customise your preferences or reject non-essential cookies. Learn more

    Loc.ai
    Sign inStart free
    Loc.ai Community

    Join the Loc.ai Sovereign AI Developer Community

    Developers, founders, and enterprise teams building AI on infrastructure they control. Get help, ship faster, and shape the roadmap for Loc.ai:Control and on-device inference.

    Where the community lives

    Discord

    Real-time chat with the Loc.ai core team and other developers shipping sovereign AI on their own infrastructure. Get help with Loc.ai:Control deployment, model loading, quantisation, and on-device SDK integration.

    Join Discord

    GitHub

    Open issues, follow releases, read source for our SDKs and example apps, and contribute pull requests. The fastest path to influencing the roadmap.

    Open GitHub

    YouTube

    Walkthroughs covering sovereign AI architecture, Loc.ai:Control deployment, benchmark deep-dives, and live build sessions.

    Watch on YouTube

    Documentation

    Reference docs, integration guides, and the OpenAI-compatible API spec. Includes runnable examples for SaaS, enterprise sovereign deployments, and offline scenarios.

    Read the docs

    Who's in the community

    SaaS founders cutting inference spend

    Move chat, summarisation, and embedding workloads off per-token cloud APIs and onto the user's device via the Loc.ai SDK. Community members regularly share margin and latency numbers from real production cut-overs.

    Enterprise teams running sovereign AI

    Discuss Loc.ai:Control deployments, air-gapped setups, audit logging, UK GDPR, EU AI Act readiness, and sector-specific constraints in healthcare, legal, and finance.

    Developers shipping offline-first AI

    Patterns for hybrid routing, model selection per device class, fallback when local compute is insufficient, and storage of quantised weights.

    Contributing

    Loc.ai publishes SDKs, integration examples, and tooling under github.com/locai-co-uk. Contributions are welcome — issues, pull requests, benchmark reproductions, and example apps.

    1. Open or comment on an issue describing the change.
    2. For non-trivial work, drop a note in Discord to align with the core team.
    3. Submit a pull request with tests and a short rationale.
    4. Larger features ship behind a flag until they're stable across edge targets.

    Frequently asked questions

    Does Loc.ai have a developer community?

    Yes. The Loc.ai community is active on Discord, GitHub, and YouTube. Discord is the primary channel for real-time help and roadmap discussion, GitHub is where issues and pull requests are handled, and YouTube hosts longer-form walkthroughs and build sessions.

    How do I contribute to Loc.ai?

    Start in GitHub at https://github.com/locai-co-uk. Open issues for bugs and feature requests, or submit pull requests against the SDKs and example apps. For larger contributions, join the Discord first to align on scope with the core team.

    Where can I get help integrating Loc.ai?

    The Discord server is the fastest channel for integration questions. The documentation at https://docs.locai.co.uk/docs/ covers the OpenAI-compatible API, hybrid routing, and offline deployment. Enterprise customers can also reach the team at hello@locai.co.uk.

    Is Loc.ai open source?

    Loc.ai publishes SDKs, example apps, and integration tooling on GitHub at https://github.com/locai-co-uk. The hosted control plane and proprietary edge runtime are commercial, with a Free Forever Developer plan available at https://control.locai.co.uk.