Login One

Research

Research we can ship.

We work on applied AI, language tools and the infrastructure under our products. What proves useful goes into those products and out as open-source packages anyone can install.

Focus
Applied AI, language tools, developer infrastructure
Output
Open-source packages, used in our own products first
Not doing
Robotics and space are direction, not active work

What we work on

Six areas, each with code you can read and install today.

  • AI building blocks

    One way to talk to any model: chat, streaming, prompts, token budgets, tool definitions and repairing the JSON models return.

  • Retrieval & agents

    Splitting, embedding, storing and reranking documents, and a small agent loop that can call your own tools.

  • Cheaper AI

    Spending fewer tokens: cheap checks before a model call, caching repeated calls, condensing sources and failing over between providers.

  • Language & dates

    Nepali and English names across scripts, Bikram Sambat dates, and reading when an article was really published.

  • Trust & checks

    Redacting personal data, catching prompt injection, and checking that numbers and names in generated text match the source.

  • Reliable software

    Zero-dependency libraries and a testing kit, so what we publish stays small, auditable and easy to keep up to date.

The work, as packages

A selection from the catalogue, grouped by area. Each one is zero-dependency and documented on developer.lacspace.com.

Full catalogue

31 packages

Where it runs

The same pieces, working inside things people use.

Lacspace Mail
Lumi AI summaries, drafts in your tone, translation and a pre-send review; phishing checks on SPF, DKIM and DMARC; smart categories.
lacspace.com
Lumi, the assistant on this site, answers questions about Lacspace and its products.
StockYatra
Lumi AI inside the trading simulator, with more of it on the Pro plan.
Newsroom tools
Briefs, fact-consistency checks, date checks and name matching built for an AI-assisted newsroom, then published as packages.

How we approach it

Cheap checks first
A lexical screen, a cache or a deterministic rule runs before any model call. The model handles only what is left.
Bring your own model
Our AI packages hold no keys and favour no provider. You choose the model, and can change it later.
Zero dependencies
Each package stands alone, so installs stay small and there is less to audit or patch.
Publish what we use
If we build a piece for our own products and it is useful elsewhere, it goes out as an open-source package.
Measure the output
Generated text is scored and checked against its source rather than trusted because it reads well.

Before we build a product

Product research is less glamorous: three questions answered before a timeline is promised.

  1. 01

    Who it is for

    Interviews and walkthroughs with the people who will use it day to day.

  2. 02

    What already exists

    A review of competing products, their pricing and where their users complain.

  3. 03

    Is it buildable

    A technical spike on the risky parts before a timeline is promised.

Where it is heading

Software, then AI, then robotics, then space. The first two are today's work; the last two are direction, not programmes.

  1. Today

    Software

    Products and client systems, and the open-source tools under them.

  2. Today

    AI

    Applied AI inside those products, and the packages on this page.

  3. Direction

    Robotics

    Where we want the work to lead. Not an active programme today.

  4. Direction

    Space

    The long horizon. Not an active programme today.

Building with AI, or want to work on this?

Use the packages, tell us what is missing, or come and build them with us.