OAIY

What is OAIY?

OAIY stands for Orchestrate AI Yourself. It combines visual flow editing with connections to local models, provider APIs, services and device plugins. Instead of assuming one model or one remote service, it provides a workspace in which those choices can become reusable parts of an automation.

The browser editor and the local runtime have different responsibilities. The editor is where you design and inspect a flow. OAIY Desktop can install or supervise local services, manage models and Python environments, and make approved capabilities available to connected applications. A CLI and a headless server support execution without keeping the editor open.

Build flows that do more than ask a model

A workflow can combine model calls with HTTP requests, transformations and approved device actions. That makes OAIY useful as an orchestration layer around inference, not just a chat interface. The execution engine is shared between its browser and CLI paths, with host adapters supplying the capabilities available in each environment.

The optional backend provides shared flow snapshots and a remote run queue. A browser dispatcher or CLI worker executes queued work against its configured services. Inference still takes place at the selected local server or provider; the sharing service is not itself the model runtime.

• Connect a local OpenAI-compatible server or a supported provider profile.
• Install and supervise supported local services from Desktop.
• Download models and manage associated runtime settings.
• Run saved flows through the CLI or a headless deployment.
• Inspect connection state, plugin health and execution logs.

Pair a browser. Link an account. Keep the distinction.

A browser connection grants an approved web application access to the local runtime. An account link gives OAIY scoped access to a service such as FormLogic for records, events and connected automations. These are separate permissions, even when both are part of one setup experience.

For remote use, OAIY can make outbound HTTPS connections to a linked FormLogic site. A phone or another computer can then use the account-backed path without reaching a localhost port on the OAIY machine. The machine must remain running and connected. This is not a promise of unattended availability when the local host is asleep or offline.

The remote FormLogic integration documents end-to-end encryption for AI requests and relay flow inputs/results. Service or plugin commands and account records follow their authenticated HTTPS paths. Those distinctions matter: one encrypted channel does not imply that every field across the ecosystem is end-to-end encrypted.

A local runtime for capabilities a browser cannot own

Plugins let OAIY supervise a process with a defined contract rather than letting a website take arbitrary control of a machine. Aokie is the phone integration: it connects the supported Bluetooth hardware, supplies the voice loop and emits durable events. FormLogic can turn those events into business records and follow-up flows.

Models and speech services need compatible APIs and real configuration. A saved provider entry is not proof of successful inference, and selecting a local endpoint does not guarantee GPU execution. Test the actual provider response and the service capabilities before depending on them in a workflow.

Use only the runtime you need

The web UI can run without the optional sharing backend. Desktop adds process and device management. The CLI provides headless flow execution, while the Tauri-free oaiy-server binary exposes local runtime services without a desktop window. The separate PHP API adds shared snapshots and queued requests.

The headless server requires authentication for protected routes. Shared edit links should be treated as credentials because they can authorise changes or execution. Enable sharing deliberately and review which local capabilities a flow can invoke. Do not turn an internal runtime into an unauthenticated public endpoint.

Start with one provider and one small flow

Configure a local model server or a provider in OAIY Desktop and use the Test action to confirm that it responds. Build a small flow whose output you can inspect. Connect FormLogic only after the local path is working, then complete browser approval and the linked-account step required by the intended workflow.

The current provider gateway exposes chat-completion capabilities. It is not a general realtime WebSocket voice proxy. Aokie’s working local speech path uses separate speech recognition, language-model and text-to-speech services. Follow the current README and protocol documentation rather than assuming every older design proposal is implemented.