Questions before your first workflow.

Not for everyday use. A partner can handle technical setup and connect your systems. You define the work, rules and approval boundaries.

A chat usually begins with a question. A workflow has a defined ongoing responsibility and responds to new material or scheduled tasks. You do not need to describe each step again.

Yes, if the engine runs on another available machine, such as your server. Switching off the computer that runs the engine also stops its work.

Set permissions and approvals for sensitive actions, review outputs and handle exceptions. Autonomy does not mean infallibility or a transfer of professional responsibility.

Working context and files stay in your environment. The control channel between app and engine is end-to-end encrypted. External models and tools still receive the inputs you send them during work.

The public code has its own licence terms. Independent development and non-production testing have no licence fee under the applicable version's terms. Production use follows that version's rights and any Start or Business commercial licence.

An instance is a separate environment for one end client, not a physical server. It can contain multiple agents. Multiple client environments on a shared server require multiple licences; each additional separate production instance is billed separately.

No. Business includes a first substantive response within 16 working hours in the defined support window, not continuous on-call support, a repair guarantee or an uptime guarantee. See pricing for details.

A partner helps select the workflow and handles setup and routine care as agreed. Promptbook provides the technology and licensed product support. Independent technical deployment is also possible.

Not necessarily. Compare the approaches. Some tools, such as coding harnesses, can form part of your Promptbook solution.