Straight answers for the people evaluating Tenured.

Tenured by Ignite9 provides digital employees for enterprise applications: production support, modernization and compliance. Digital employees take production tickets, follow each one through the business process across your systems, and build the fix in development with its unit test. Your people approve the move to QA and the tested change, and a named person in your IT team deploys to production. Tenured Code Remediation moves custom code from SAP ECC to S/4HANA and clean core, from Oracle E-Business Suite to Fusion, and from legacy systems to Salesforce and Workday. Tenured E-invoicing handles SAP Document and Reporting Compliance and e-invoicing mandates.

Tenured’s capabilities are delivered through design-partner engagements: scope and timing are confirmed when we scope your work. Book a scoping call and we will start with one support process and the people accountable for it.

In SAP ECC and SAP S/4HANA, digital employees work with their own SAP users, through machine routes first (your vendor’s MCP servers and APIs, then transports and tables read through the SOAP-RFC service) and SAP’s own screens (SAP GUI for HTML) as the fallback. They diagnose incidents from SAP’s own logs, build configuration and ABAP changes in development with their unit tests, move them to QA on your approval, verify your user’s test in SAP and hand the tested change to your IT manager. They explain your custom code from the code itself, build RAP and CDS on your own objects, write analyses up as Word and PDF documents, and answer read-only look-ups of exchange rates, bank cash, payment runs, bank statements and your SAP eDocument status.

Included connector profiles cover SAP S/4HANA Cloud, SAP Ariba, SAP Concur, SAP SuccessFactors, Salesforce, Workday and Oracle, and ticket sync covers ServiceNow and Jira. A connector catalogue from public API and MCP directories adds more than 31,000 entries. Your administrators review and enable each connector before use. On vendor policy, Tenured adds no restriction of its own: SAP’s authorizations decide, your own custom objects (Z and Y names) and SAP’s screens are never gated, and an interface SAP’s published policy prohibits, such as ODP-RFC, is used once you confirm with SAP that your contract permits it and an administrator records that.

No. Tenured works with them both ways: it reads new tickets, writes its progress and resolution back, and the caller confirms or reopens the ticket in ServiceNow or Jira as usual.

Tenured has twelve launch languages: English, Arabic, German, French, Hindi, Chinese, Spanish, Russian, Italian, Portuguese, Dutch and Polish. It detects the language of each message and answers in it, and specialists read a translation into your working language beside the original.

The AI desk answers 24/7, and people answer during your support hours. If a model provider is down, a backup model you registered takes over. If none is available, logged requests are still acknowledged with their reference and wait until a model answers or a person takes them.

You choose: Claude, OpenAI, Gemini, DeepSeek or any model with an OpenAI-compatible API, including one you host yourself, once its address is on the approved list. You use your own keys, choose the model for each role and set backup models for outages; only backups inside your data boundary qualify.

Tenured runs as Ignite9’s hosted service on Google Cloud, with sign-in through Microsoft Entra ID, or as the client-hosted option: a single-VM bundle delivered during onboarding, in which model calls go only to the model hosts your administrators list. Dedicated or in-country hosting is discussed with Ignite9 case by case; we make no data-residency commitment.

Each client sets a data boundary: for all data and for each class of it, from internal information to bank details, whether a model may receive it, in which regions and in which kinds of destination, from your own hosting to a vendor’s API. Tenured checks it before each model call, each call to a Tool Hub tool and each voice session or phone call, refuses what it does not permit and records every refusal.

Only where your data boundary permits it. Sensitive data stays within the boundary your organization sets, and Tenured checks that boundary before every model call. The credentials Tenured uses never reach a model, no model call carries an image, and bank account numbers are masked in what people receive by default.

Deterministic first: rules, reviewed routines, code and API reads come before a model call. A cost ledger records what every model call cost, and an efficiency report shows the work done without a model. Your organization sets monthly model budgets, with alerts at 50, 80 and 95 percent of the budget, and chooses the model for each role.

Yes. Tenured Mergers & Divestitures compares the custom code of two estates after a merger, traces a divestiture’s carve-out boundary through the code with an organizational-key analysis, and prepares the carve-out set and its adapters, under a written authorization covering every estate. See /tenured/mergers-and-divestitures/.

We do not claim any certification. Every change to Tenured passes separate QA and security reviews by review agents, with automated tests and security scans, before it ships, and releases are signed. The sealed audit trail lets your auditors check the record themselves.

Book a scoping call. We start with one support process and the people accountable for it.