TENURED BY IGNITE9 · SECURITY AND GOVERNANCE
Security, data and hosting.
Tenured by Ignite9 (digital employees for enterprise applications: production support, modernization and compliance) keeps your people in authority over your systems: access you grant, approvals with segregation of duties, a sealed audit trail, a data boundary you set, and your choice of models and hosting.
IN SHORT
Built into every digital employee, not added on.
Guardrails around every workspace
Every digital employee works in its own isolated, locked-down workspace. It reaches only the systems and addresses you approve, and every action with an effect is recorded.
Sensitive data protection
You decide which data each AI model may receive and where, and Tenured checks it on every model call. Credentials never reach a model, and bank account numbers are masked in the answers and reports people receive.
Lower AI cost
Repeated work is done by rules and reviewed routines instead of AI, and every AI call is priced, so you see the cost saved next to the work done.
Memory that builds on past work
Your digital employees remember the verified outcomes of past work, so each project starts from what the last one learned. Memory never overrides your current data or your access rules.
01 / YOUR DATA AND AI MODELS
What reaches an AI model is your decision.
Your organization sets a data boundary, and Tenured checks it before a model receives your data: for each class of data, whether a model may receive it, in which regions and in which kinds of destination. Sensitive data stays within the boundary your organization sets. The credentials Tenured uses never go to a model, and no model call carries an image.
You set where each class of data may go
For all data and for each class of it, from internal information to personal data, pay and bank details, your administrators decide whether a model may receive it, in which regions, and in which kinds of destination: your own hosting, your cloud tenancy, a vendor’s API or an aggregator, each under the retention and training terms they record for it. A term nobody recorded never satisfies a rule that restricts it.
Checked before every model call
Tenured checks your policy before each model call a digital employee, a look-up, a translation or a report draft makes, before each call to a Tool Hub tool, and before a voice session or phone call starts. It refuses what the policy does not permit and records every refusal.
The credentials Tenured uses never reach a model
The passwords and keys Tenured uses for your connections, your applications’ sign-ins and your model endpoints never go into what a model is sent, and Tenured removes them from what connected tools send back, error messages included, before a model sees them.
No screenshot is sent to a model
No model call carries an image: what a digital employee reads from a screen reaches its model as text. Screenshots are kept as evidence in the request’s files, and a requester sees only those taken in their own sign-in or those your operators choose to show them.
Only verified models, at approved hosts
A model receives work only after your administrator has verified its endpoint, and only at a host on the approved list. A model you host yourself joins once its address is added to that list.
Bank account numbers masked in what people receive
By default, Tenured masks bank account numbers and IBANs to their last four characters in a look-up’s answer, the files it carries and a request’s report. Your administrators can show them in full, which counts as widening your policy.
Voice through OpenAI’s realtime API
Browser and phone voice use OpenAI’s realtime API: what a caller says goes from their browser or phone carrier straight to OpenAI, not through Tenured. Before a session or call starts, Tenured checks your policy, counting live voice as personal data.
Your own network, in the client-hosted option
In the client-hosted option, delivered during onboarding, model calls go only to the model hosts your administrators list. Where they list only a model you run yourself, model traffic stays inside your network.
02 / THE CONTROLS
Digital employees, governed like employees.
Access you grant, step by step
Each digital employee holds only the access your security team grants. When a ticket needs more, it asks the team that owns that access for the least access for the shortest time, with the ticket’s context. If the team declines, the team does the work itself from a complete work package. A digital employee never grants or approves its own access, and never uses access it does not hold.
Production stays with your people
In Tenured’s delivery flow, digital employees never deploy to production: a named person in your IT team deploys each change they deliver. Routine standard changes your organization lists in advance, such as unlocking a user, run in production under that listing. Outside development, other writes follow the authority your administrators give each digital employee, and an action classed irreversible always waits for a person. In your development systems, the application’s own authorizations decide.
Approvals and segregation of duties
Whoever builds a change never approves it. In the delivery flow, the requester approves the move to QA on the change’s unit-test evidence, or, in an organization of more than ten people or one that turns four-eyes on, someone else does; the user who tested the change in QA approves the tested change. Activating a ticket sync needs a second administrator, and so does every sensitive setting wherever four-eyes is on. A one-administrator team’s solo mode replaces that second administrator with a waiting period, a fresh multifactor sign-in and a notice to its security contact. Every action passes a policy gateway that allows it, requires approval or denies it.
A sealed audit trail
Every action with an effect, every gate and every decision is stamped by the database’s own clock and sealed into an append-only hash chain for each client, with signed seals. Your auditors export the seals with their events and verify them offline, and your SIEM collects the latest seals from Tenured’s audit API.
Change windows and a pause switch
Change windows and blackout periods decide when digital employees may act, and an organization-wide pause switch stops every digital employee at once.
Connectors reviewed before use
Every connector, from the included profiles to the more than 31,000 catalogue entries from public directories, is reviewed and enabled by your administrators before a digital employee may use it. On vendor policy, Tenured adds no restriction of its own in SAP: SAP’s authorizations decide what a digital employee can do, your own custom objects (Z and Y names) and SAP’s screens are never gated, and an interface SAP’s published policy prohibits is used once you confirm with SAP that your contract permits it and an administrator records that.
Honest about AI
Status updates, digital employees’ replies and every comment, work note and resolution note a ticket sync writes carry your organization’s AI disclosure. Every call begins with a disclosure and asks for consent before anything is stored.
03 / HOSTING
Where Tenured runs
Tenured’s hosted service
Ignite9 runs Tenured on Google Cloud. Sign-in to the console goes through Microsoft Entra ID.
Client-hosted
A single-VM bundle delivered during onboarding, in your own environment. Model calls go only to the model hosts your administrators list.
Dedicated or in-country
Dedicated or in-country hosting is discussed with Ignite9 case by case. We make no data-residency commitment.
04 / MODEL CHOICE
The model is yours to choose.
Tenured works with the model your organization chooses, under your keys and inside your data boundary. How Tenured keeps AI costs predictable.
Your choice of model
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.
Your own keys
Your organization uses its own model keys and chooses the model for each role.
Backups inside your boundary
Backup models you register take over when a provider fails, and only backups inside your data boundary qualify.
Every call costed
A cost ledger records what every model call cost, beside the work done without a model.
05 / ASSURANCE
What we claim, and what we do not.
Reviewed twice
Every change to Tenured is reviewed separately for quality and for security, by a QA review agent and a security review agent, and goes through the automated tests and security scans before it ships. Releases are signed.
No certification claims
We do not claim SOC 2, ISO 27001 or any other certification. We walk your security team through the controls and the evidence instead.
Evidence you can check
Your auditors check the audit trail themselves: they export the signed seals and recompute them offline. Keep each new seal in your own SIEM, and records already sealed and shipped there cannot be removed unseen.
Report a concern
Email smaan@ignite9.io. How this website itself handles information is on the website security page.
NEXT STEP
Bring one ticket that bounced between five teams.
In a 30-minute demo we show Tenured at work, walk through how it would handle yours, answer your security team’s first questions and agree the scope of a design-partner engagement.
