Frequently asked questions

Neota Logic is a visual development platform for automating professional work. Legal, compliance and risk teams use it to build secure, enterprise-grade applications across three pillars — Processes, Knowledge and Documents — without writing code.

No. Authors build in visual tools like process maps and decision trees. Developers are welcome and can extend solutions through APIs and integrations, but they aren't a prerequisite for shipping.

Anything that combines rules, documents and workflow: intake and triage, contract generation and negotiation, regulatory assessments, approvals, and self-service advice apps.

Studio and Architect are Neota's application building environments. Workflow is the orchestration layer that connects your Neota apps to internal and third-party systems. Alongside these, NDM stores your data and the document automation tools generate your documents.

Neota generates complex documents from your templates, driven by the answers and rules in your workflow, so a document comes out correct the first time. The Word Toolbar brings that authoring into Word itself, so the people who own the templates maintain them in the tool they already use.

You point an AI task at a specific job inside a workflow: read a contract and pull out the clauses, classify an intake request, draft a summary from a matter file. The workflow decides when that task runs, what it receives, what happens to the result, and which steps still need a person. The model does the language work. Your rules decide the outcome.

Every run is logged: the inputs, the rules applied, the AI tasks that ran, and, where you have built review into the app, who approved what. When a regulator, client, court, insurer or your own board asks what happened, you can show the trail rather than describe it.

Yes, and we think it is critical. A reviewer should have full insight into what the AI produced and what the workflow did with it, not just a yes or no button. You decide where those review points sit, who owns them, and what the app does when a check doesn't pass, whether that means routing to a named person, holding the matter, or asking the requester for more.

Neota is model-agnostic. Deployment sits inside your own AWS Bedrock or Azure boundary and connects to frontier models including Claude and GPT, so your AI runs under the cloud and data agreements you already have in place.

No, and the structure is what makes that true. Neota doesn't send your data to a Neota model. You connect your own model under your own provider agreement, so whatever data protections you already negotiated stay exactly as they are.

Neota runs on AWS with regional hosting options, backed by a Postgres or MS SQL data layer. Deployment region is chosen to fit your data residency requirements.

Two levels. Access to building in Neota is managed in Workbench with role-based permissions, and single sign-on is supported so accounts follow your existing identity provider and offboarding process, though SSO isn't mandatory. Access to the applications you build is entirely yours to define, down to who can start a workflow, who can see a matter, and who can approve.

Yes. Workflow connects Neota apps to internal and third-party tools and databases through REST APIs and prebuilt connectors, including document management, e-signature and CRM systems.

Prebuilt connectors include Microsoft 365 and SharePoint, Salesforce, DocuSign and Adobe Sign, iManage and NetDocuments, Slack and Teams, plus Azure and Amazon Bedrock for AI. Anything with a REST API can be connected directly from Workflow, and Neota apps expose their own APIs so other systems can call them.See the integrations page for the full list.

Most teams have a working first application within weeks, not quarters. Scope matters more than complexity — a focused intake or document app moves fastest and builds internal momentum.

Neota University covers author training and certification, and Building Blocks give you tested starting points. Our team also works alongside yours on early builds.

Pricing is tailored to the scope of your deployment — solutions in scope, users and environments. See the pricing page for the model, then talk to us for a figure that reflects your setup.

Bring a real process with a known cost. We'll walk through how it would be built, what the audit trail looks like, and what your team would own after go-live.