Getting Started with NOWORX
NOWORX is AI-agent groupware where team-level AI agents work together on your org chart. There are just three things you need to understand.
1. Org Chart — Teams and Agents
Create teams that mirror your workspace's structure (Finance & Accounting, HR & Labor, Marketing, etc.) and assign an AI agent to each one. The agent becomes the person in charge who understands that team's work.
2. Chat — Giving Instructions
Send an instruction through chat on the app, web, or desktop, and the responsible team's agent carries out the task and reports back with the result. Groupware features like mailbox, calendar, attendance, approvals, and drive are built in.
3. Launcher — Execution Engine
The launcher installed on an office PC is the engine that actually executes the work. The app and web are the remote control that issues instructions; the launcher is the heart that processes them.
In short — create teams in the org chart → assign agents → give instructions through chat, and the launcher handles the actual work.
Installing the Launcher (Engine)
The launcher is a program that turns an office PC into an engine that executes real work. Download and install the Windows or Mac version from the downloads page.
After Installation
After signing in with your workspace account, the launcher waits in the background (system tray). When an instruction arrives, it processes the task and reports back the result. It automatically updates to the latest version while running.
Why an On-Premise PC
Because sensitive credentials (passwords, hosts) are kept only in the on-premise launcher and never sent to the cloud. This preserves data sovereignty and security.
What Is a Connector? — The Agent's Pathway
A connector is the "pathway" that lets an agent attach to an external business system (Douzone, SAP, QuickBooks, internal DBs, SaaS) and explore and reason on its own. Rather than hard-coding a fixed set of lookup functions, it opens a door and a map so the agent can figure out what it needs, on the fly.
The NOWORX connector format (.aqc) consists of three layers.
① ACCESS — How to Connect
Connects using a verified adapter (MSSQL, PostgreSQL, MySQL, REST, etc.). Only the schema for connection fields (host, account, etc.) is defined — the actual password is never stored in the manifest.
② DISCOVER — What's There
This is how the agent scans the system on its own. For a database, it reads the schema (tables, columns) to understand the structure; for a SaaS system, it looks at the API list. This means you can ask anything through a single pathway — sales, inventory, receivables, whatever you need.
③ GUARD — What's Allowed
Enforces read-only access, whitelists the allowed scope (tables/endpoints), and masks sensitive data. This sets a safe boundary so the agent can explore freely without risk.
There's no need to trust server code running somewhere, like with MCP. Because NOWORX connectors are declarative and use verified adapters, data leakage or destruction is structurally impossible even when you install a connector someone else made.
Connecting a Connector
Click the Data Integration button in the bottom-right of the org chart screen to open the list of connectors.
1. Select and Activate
Select and activate the business system you want to connect. You can find it by category or search.
2. Enter Connection Details
When you enter connection details, they are sent directly from the browser to the on-premise launcher and stored in the launcher's vault (DPAPI). Passwords never pass through the cloud or any server.
3. Use the Agent
Once connected, the team agent queries that system's data read-only and puts it to use in its work.
Connector Studio · Publishing
There are three ways to build a connector, and all of them produce the same .aqc manifest.
① Auto-Generate (Non-Developers)
Just enter the connection details, and the agent automatically explores (DISCOVER) the system to draft a connector for you. You can build your own workspace's pathway even without knowing SQL.
② Form Builder (Admins)
Build it on screen by filling in connection fields, discovery options, and safety boundaries.
③ Manifest (Developers, Vendors)
Write the .aqc file (JSON/YAML) directly or upload it as a file. It can be shared with your team or via Git.
{
"id": "duzon-icube-kr",
"name": "더존 iCUBE",
"publisher": "your.co",
"category": "erp",
"access": { "adapter": "mssql", "fields": [ /* host, database, user, password ... */ ] },
"discover": { "mode": "introspect", "hints": { "sales": "sales_*" } },
"guard": { "readonly": true, "allow": ["dbo.*"] }
}
A connector you've built can be published to the marketplace (public) or registered for workspace-only use. This opens up a connector marketplace where other users install connectors built by vendors and partners. Before publishing, it must pass automatic validation (adapter whitelist, read-only enforcement, discovery scope).
※ Connector creation and publishing features are rolling out in phases. Please contact us for vendor/partner registration.
Security — Credential Boundary
Credentials Stay in the On-Premise Launcher Only
Connection passwords and hosts are saved from the browser only to the on-premise launcher (DPAPI) and are never stored in the cloud, on a server, or in a database.
Read-Only · Whitelist
External system integrations are enforced as read-only, querying only the allowed scope. Data cannot be modified or deleted.
Verified Adapters Only
Connectors run only through verified adapters. Since there is no arbitrary code execution, it's safe to install a connector someone else made.