Question 1

Does JUTSU write anything back to our systems?

Accepted Answer

No. Every connector is read-only. JUTSU builds its own graph alongside your tools and never modifies a document, ticket, message or calendar entry.

Question 2

Can people see things they should not?

Accepted Answer

No. Permissions are inherited from the source system at ingestion and enforced again at query time, so a result only surfaces for someone who could already open the underlying document. Access binds to your existing SSO and identity provider.

Question 3

How is this different from enterprise search?

Accepted Answer

Search returns documents. JUTSU keeps a temporal graph of who decided what, when and why — so it answers questions no index can: who owns this, what did we already try, and what breaks if this person leaves.

Question 4

What happens to a departing colleague's knowledge?

Accepted Answer

The knowledge-risk view scores bus-factor continuously, so exposure is visible before a resignation rather than after. When someone does leave, the Handover Generator drafts a cited pack of their open items, decisions, stakeholders and known gotchas.

Question 5

Where does our data live?

Accepted Answer

In your own deployment. JUTSU is containerised and runs in your cloud or VPC, with encryption at rest and in transit, PII masking during ingestion, and a full audit trail. Aligned to the DPDP Act 2023 and GDPR.

Question 6

How long does a pilot take?

Accepted Answer

Twelve weeks from first connector to an end-to-end deployment, scoped around a single department so the value is provable before it spreads.

Choose how you're joining