In testingNectarBox by IT Labs India

Features, and where each one stands.

Each feature has a stage. Nothing is marked “Available now” yet: version 1 runs on our test box.

One door to models

Every app calls one address. The product picks the model.

Standard chat doorIn testing

Any app, script or bot that speaks the standard chat API format most AI apps already use can switch to it by changing the address and the key. Answers in a fixed data shape are supported. The model is chosen by setting, so apps need no code change.

A key for every app or botIn testing

A person makes a key for each app, script or bot and sees it once. Keys can be suspended, revoked or handed to a colleague. There are no shared keys, so every call traces to one person.

Built and in testing. Anything that does not pass testing will be removed.

Private by default

Version 1 uses local models only, and keeps no text unless you ask.

Local models onlyIn testing

Answers come from models running in house, on the server set up for you. No cloud AI provider is configured in version 1, so no prompt or answer is sent to one.

Client wallsIn testing

One client’s requests, records and cost never reach another client. Every record is fenced by person and by place (organisation, client). Our staff manage accounts and seats but never read prompts, answers or logged text.

Text log only when switched onIn testing

By default only the facts of a call are kept: who, which model, how many tokens, when. Prompts and answers are logged only if your organisation and that app’s key both switch it on, and then only the key’s owner sees them.

Built and in testing. Anything that does not pass testing will be removed.

Usage and sign-in

Know who uses AI for what, and sign in without passwords.

Usage per person, app and organisationIn testing

Calls and tokens are counted per app key, per person and per organisation and shown on a usage page. Daily totals are meant to go to your IT Labs India account for billing; that link is still being connected.

Passkey sign-in and welcome linkIn testing

A person opens the welcome link, sees their account, organisation and the link’s expiry, and makes a passkey (fingerprint, face or screen lock). No passwords to leak. A first-use card and a help page with an example call guide the first key. If a passkey is lost, staff send a new link and the person’s keys stay unchanged.

Built and in testing. Anything that does not pass testing will be removed.

Want to see it on your own apps?

A pilot, set up with you and scoped to your needs.

Book a pilot