# NONA — Hybrid integration platform

> NONA is a hybrid integration platform for building and running workflows visually across APIs, databases, queues, cloud and on-premise systems.

- **Connect systems** — NONA is a hybrid integration platform. APIs, databases, events, queues, cloud and on-premise environments in one place.
- **Compose workflows** — Connections come together as visual processes: branching, data transformation, AI nodes and an execution log.
- **Grow step by step** — Start with a single exchange. Sources, conditions, actions and execution control are added without rebuilding the integration.
- **EVENT** — A webhook, a record change, a queue or a schedule starts one observable process.
- **LOGIC** — NONA transforms data, checks conditions, calls the systems or AI it needs and controls branching.
- **ACTION** — The workflow updates a system, passes the event on and records the execution result.
- **EXECUTION LOG** — STATUS · VERSION · INPUT · OUTPUT · ERROR · RETRY
- **Plug in AI** — The model receives prepared context. What comes back is a structured result, a decision or an action: the workflow validates it and continues by the rules you set.
- **Stay in control** — Execution is not buried in scattered scripts. You see the version, the input, the result, the error and the retry.
- **DEPLOYMENT** — Cloud, your own environment or a hybrid — without breaking the workflow.
- **LOG AND RETRIES** — Status, error, input and output of every node. Retrying is safe.
- **ACCESS AND SECRETS** — Roles, connections, secrets and audit are kept apart from workflow logic.
- **VERSIONS AND SCALE** — A workflow is tested, published by version and scaled with the load.
- **Connect anything**
- **APIs and systems** — Links products already in use without rewriting their internal logic.
- **Event-driven processes** — Reacts to webhooks, queues, schedules and data changes.
- **Data preparation and AI** — Collects context, calls the model and continues the process from the result.
- **Hybrid infrastructure** — Joins cloud and on-premise environments with access and execution under control.
- **Ask what matters** — Platform boundaries, rollout order, available nodes and where it runs — the four questions we hear most often.
- **Does NONA replace the corporate systems already in place?** — No. The platform connects them through visual workflows and moves integration logic into a managed process. Every system keeps its own responsibility.
- **Can we start with a single integration flow?** — Yes. The setup can grow in stages: from one critical exchange to the company-wide event and API architecture.
- **Which nodes can a NONA workflow use?** — Triggers, connections, transformations, conditions, branching, actions, AI nodes and error handlers. The exact set depends on the project infrastructure.
- **Where can the platform run?** — In your own infrastructure, in the cloud or in a hybrid setup. Where the boundary sits is decided by security, data and resilience requirements.
- **Start with one** — Describe the event, the systems, the data and the action you expect. We will draw the workflow boundaries and name a sensible starting point.

## Documents
- [Personal data](https://nona.tech/personal-data)
- [Cookies](https://nona.tech/cookies)
- [llms-full.txt](https://nona.tech/llms-full.txt)

## Contacts
- winwin@nona.tech
- NONA TECH LLC, 196006, St Petersburg