FAQ

Tap any question to expand the answer. Use the browser's Find in Page (Ctrl/Cmd + F) to search across all questions, including closed ones.

• Is Exekra cloud-hosted or on-premise?

  Exekra runs 100% on-premise inside the organization's own infrastructure. Studio, Hub, and the workflow runners install on Windows machines on the customer network. Workflow data, credentials, and execution logs never leave the firewall.

• What operating systems does Exekra support?

  Studio, Hub, and runners install on Windows 10, Windows 11, and Windows Server 2016 or later. The platform is designed for organizations standardized on Windows for desktop and back-office automation.

• Do I need to write code to build automations in Exekra?

  No. Exekra Studio is a fully no-code visual designer. Workflows are built by dragging activities onto a canvas, connecting them, and configuring properties. The activity library covers browser, Excel, database, email, file operations, and external integrations.

• How does Exekra handle security and compliance?

  Role-based access control, encrypted credential storage, and a complete audit trail of every workflow execution are built in. Because everything runs inside the customer network, data residency and sector-specific compliance requirements stay under the customer's control rather than the vendor's.

• How is Exekra different from UiPath, Automation Anywhere, or Power Automate?

  Exekra is on-premise by design, not a cloud-first product with an on-premise option bolted on. Pricing is per cap (runners, Studio seats, attended users) rather than per task or per bot, which makes it predictable for mid-market organizations that don't want seven-figure enterprise RPA contracts.

• How is Exekra priced?

  Pricing is per cap with independent limits on unattended runners, Studio developer seats, and attended users. Annual contracts include volume discounts, the full workflow studio, all activities, and on-premise deployment. There are no per-task fees or overage surprises.

• Can the system run without internet access?

  Yes. After initial license activation, the platform operates entirely offline. All components run within the organization's network.

• How are workflows versioned?

  Each save creates a new version with an auto-incrementing number. Versions are classified as draft (in-progress) or published (executable). Only one version per workflow can be published at any time. All versions are retained for audit and rollback.

• Can production be isolated from development?

  Yes. Deploy separate hub instances for each environment, each with its own database, runners, and license. Promote workflows by exporting and importing graph definitions.

• How does scaling work?

  Add more runners to increase execution capacity. The hub assigns work automatically. Each runner adds one concurrent execution slot.

• What happens if a runner goes offline?

  ASSIGNED executions are re-queued once. RUNNING executions get a 5-minute grace period. If the runner does not recover, executions are marked FAILED. The runner reconnects automatically when network connectivity is restored.

• Can multiple workflows run simultaneously?

  Yes, with N online runners, up to N workflows can execute concurrently.

• What is the backup strategy?

  Primary: regular PostgreSQL backups. Configuration files (hub-config.json, .env, TLS certs) should be backed up separately. Redis data is transient and does not require backup.

• Can I migrate the hub to a new server?

  Yes. Back up the database and configuration files, install on the new server with the same configuration, restore the database. Runners reconnect automatically if the access URL remains the same.