Contact Us

Tell us about the work.

Send us the systems involved, what you want automated, and the constraints that matter, such as data that may not leave your machines. The next step is a scoping conversation, not a proposal you have to read first.

Emailhello@openeng.ai

One mailbox, read by the people who do the work. There is no form: plain email is fine.

Routes

Choose the conversation.

Each card opens a message with the subject already set, so your note lands in the right thread on the first send. Product support has its own doors.

  • email

    Services

    AI automation and custom AI: recurring automations on the OpenEng AI engine, built from global loops, cells, and connectors; open-source tooling adapted to your business; and private AI on your own Linux x86_64 machines.

    SubjectServices: AI automation

  • email

    Research collaboration

    Joint work on agentic systems and governed execution, open-weight models, sandboxing, or the AEL compiler. Tell us the question you are working on and what you have so far.

    SubjectResearch collaboration

  • email

    Press and partnerships

    Interviews, briefings, and partnership proposals. Include your outlet or organization and the date you are working toward.

    SubjectPress and partnerships

  • product hosts

    Product support

    Product questions go straight to the product hosts: documentation and a feedback site for the OpenEng apps, separate documentation for the AI engine, and the AEL status record for what is built and what is planned.

Where we are

Bangalore, by email.

We are based in Bangalore and work with teams anywhere. Every engagement starts in writing, so the mailbox is the front door.

Company

OpenEng Labs Private Limited

Bangalore, Karnataka, India

OpenEng Labs is an AI research company in Bangalore that builds agentic software on open-source foundations and brings AI automation to enterprises.

Website
openeng.ai
Engineering apps
openeng.app

No street address or phone number is published.

Map pin marking Bangalore, Karnataka, India
Bangalore · Karnataka · Indiaworks with teams anywhere

Before you write

What a good brief includes.

Four short answers are enough to scope most engagements. Rough notes are fine; the scoping conversation covers the rest.

  1. 01

    Current stack

    The tools, clouds, models, and repositories your team already runs, and the systems the automation must talk to.

  2. 02

    Target outcome

    What you want automated, and how you will know it worked: hours saved, tickets closed, a report produced on time.

  3. 03

    Data boundaries

    What may leave your machines and what may not. It decides whether models run on-device or through an OpenAI-compatible endpoint you control.

  4. 04

    Timeline

    When you need a first result, and any date that cannot move. We scope a first working slice, then widen from there.

After you send

What happens next.

Three steps, from the first reply to a written scope. We publish no guarantee on reply times.

  1. We read it

    Your message reaches the people who would do the work, not a ticket queue. If one of the four brief answers is missing, the reply asks for it.

  2. We scope it together

    A short call or an email thread, whichever you prefer, to map the systems involved, the data boundary, and the first working slice.

  3. We agree scope in writing

    What we build, where it runs (today, your own Linux x86_64 machines), and how we verify it, written down before work starts.

    scope · in writing

Starting point

No engagement starts from a blank page.

Every engagement composes from these live catalogs before anything is written from scratch. The counts were read from each catalog.json on September 25, 2026, and the status strips say what is live, in beta, and planned.

Status, as of September 25, 2026

  • Beta

    Engineering apps

    Five apps in beta, free: Terminal, Kubernetes, Data, Git, Chat

Status, as of September 25, 2026

  • Live

    AI engine

    Live on Linux x86_64; macOS and Windows builds coming; GA planned Q4 2026

  • Planned

    AEL 0.1

    In development, not released; linux-x86_64 is the sole qualified target

Questions

Three quick answers.

How to reach us, what we publish, and what a first message should carry. The full FAQ covers the products and the research.

Read the full FAQ

How do I contact OpenEng Labs?

Email hello@openeng.ai. There is no form: each card on the Contact Us page opens a message with the subject prefilled for services, research collaboration, or press and partnerships. Product questions go to the product hosts instead: docs.openeng.app documents the five OpenEng apps, feedback.openeng.app takes bug reports and feature requests for Terminal, Kubernetes, and Git, and docs.openeng.app/ai documents the AI engine.

Is there a phone number or office address?

No. OpenEng Labs Private Limited is based in Bangalore, Karnataka, India, and publishes one mailbox rather than a phone line or a street address. Every engagement starts in writing.

What should the first email include?

Four short answers: your current stack, the outcome you want and how you will measure it, which data may not leave your machines, and the date you need a first result by. Rough notes are fine, and there is no need to send credentials or production data; the scoping conversation covers the rest.

Start with one email.

Write to hello@openeng.ai with the four answers above; rough notes are fine. If you would rather read first, the services page lists what we build and how an engagement runs.