AI agents forSAP Cloud ERP.

Qubi augments Joule — we extend it, we do not replace it. Joule is SAP's conversational front door: users ask questions and kick off simple actions in natural language, inside SAP. Qubi runs the long-lived, multi-step, cross-system agents that Joule is not designed to run on its own. Joule handles the conversation. Qubi handles the execution. We're an SAP Silver Partner authorized under PartnerEdge for Sell and Service, and the augmentor framing is deliberate: we're a collaborator, not a competitor. See our dedicated Joule page for the full division of labor: /sap/joule

S/4HANA Cloud, S/4HANA on-premise, ECC, Business One, and SuccessFactors. We provide native connectors for each, including read and write operations with full audit logging. Customers running hybrid landscapes (for example, ECC on-premise alongside S/4HANA Cloud) can use a single Qubi deployment across both.

Rough guide. (1) Enterprise with strict data residency, large SAP estate, or heavy security review — choose self-hosted in your own infrastructure. (2) BTP-standardized shops with a BTP-first IT mandate — choose SAP BTP deployment. (3) Mid-market, SAP Business One, or cost-sensitive S/4HANA Cloud customers who want agents running quickly — choose SaaS, hosted in our Canadian region. We run a 30-minute discovery call and recommend a mode based on your SAP landscape, compliance posture, and timeline.

All three. (1) Self-hosted — runs in your own infrastructure (VPC, Kubernetes cluster, private cloud). Your data never leaves your boundary. This is the enterprise default for customers with strict residency, security, or compliance requirements. (2) SAP BTP — for customers standardizing on BTP-native deployments. (3) SaaS — hosted in our Canadian region with encryption at rest and in transit. SaaS is typically chosen by mid-market SAP buyers and SAP Business One shops who want the fastest path to production. The product is the same in all three configurations.

Every agent respects the SoD rules configured in your SAP environment. Agents cannot execute a combination of actions that violates policy, and every attempted action is logged for GRC review. One of our enterprise retail customers uses Qubi specifically for continuous SoD monitoring across thousands of users — the platform surfaces conflicts in real time rather than waiting for a quarterly review cycle. In SaaS mode, SoD awareness is configured during white-glove onboarding — our implementation team maps your existing SAP SoD ruleset to Qubi so the same controls apply from day one.

Yes. Qubittron is an SAP Silver Partner with PartnerEdge Sell and Service authorizations under SAP PartnerEdge. We actively co-sell with SAP account teams on SAP Cloud ERP opportunities. Customers who require a partner-led engagement can run the purchase through their existing SAP commercial relationship.

Most SAP customers start with one process — commonly AP automation, production planning, or SoD monitoring — and prove value in 4 to 8 weeks. From there, additional processes are onboarded incrementally. Because Qubi is a platform rather than a point solution, adding a new workflow does not require a new integration project.

Joule Studio is the right tool for SAP-only, conversational use cases inside the SAP environment. Qubi is the right tool when you need agents that span multiple SAP products, reach systems outside SAP, run long-lived workflows with complex branching, or operate under strict audit and SoD constraints. The two are complementary — we see customers use both.

Depends on deployment mode. In self-hosted and BTP modes, Qubi runs inside your infrastructure — your SAP data never leaves your boundary and we never see it. In SaaS mode, data is processed and stored in our Canadian region (data residency is Canadian by default) with encryption at rest and in transit; models can be called via your own keys (BYOK) or routed through a private endpoint. Enterprise customers with strict residency requirements typically choose self-hosted or BTP. Mid-market customers typically choose SaaS for speed and lower cost.

Both. A significant share of our SAP customers are still on ECC or running ECC alongside a phased S/4HANA migration. Qubi works natively against ECC and can serve as a bridge during migration — the same agents that automate ECC today continue to work against S/4HANA post-cutover. In self-hosted and BTP modes, ECC and on-premise S/4HANA are reached directly from inside your network. In SaaS mode, reaching on-premise systems typically requires a secure tunnel and a small add-on to expose relevant RFCs as APIs — our implementation team handles this during onboarding.

Enterprise SAP deployments are priced based on scope — which SAP systems, which processes, and deployment footprint (self-hosted vs. BTP). We run a discovery call, map your use cases, and return a quote within a few business days. Co-sell engagements can run through your existing SAP commercial framework.

No software, no extensions, no endpoint agents. Qubi runs the secure browser inside its own runtime (self-hosted in your infrastructure, on BTP, or in our Canadian SaaS region). Your team triggers and watches runs from the Qubi web app — any modern browser, any operating system. There's nothing to deploy on user laptops and nothing for IT to package.

Credentials are encrypted with AES-256 at rest, stored once per environment, and only decrypted in memory for the duration of a run — never written to logs, never exposed to runners. SSO and multi-factor authentication are handled automatically. In self-hosted and BTP modes, credentials never leave your infrastructure. API tokens for programmatic access are scoped and revocable at any time.

Non-technical users build most automations themselves. Open the recorder, walk through the Fiori transaction the way you normally would, and Qubi captures every click and keystroke into a reusable config. No ABAP, no scripting, no Joule Studio expertise. Developers typically get involved only for chained sequences across modules or for wiring the REST API into upstream systems like ServiceNow or CI/CD pipelines.