Questions live in the margin until answered.
Each note below distinguishes the proposed initial product from future directions and from adjacent enterprise systems.
What does Velqestra review?
Structured writes proposed by an AI agent or automation across identity and business systems. It assembles field-level before/proposed-after values, evidence, affected records, policy results, and required approvers into one versioned change set.
Does it replace IAM, ITSM, GRC, or observability?
No. Velqestra is a proposed review layer for pending writes. It does not replace the source systems, their logs, their native permissions, SIEM, workflow tooling, or customer policy authority.
Are Okta, Entra, ServiceNow, or Salesforce integrated today?
No production integration is claimed. They are illustrative system examples used to make the product category concrete; their mention does not imply partnership or endorsement.
Who retains the decision?
Humans designated by the customer. The customer determines which roles may approve each system and risk class, which checks are deterministic, and when a request must be rejected, changed, or escalated.
Does Velqestra execute or roll back changes?
Not in the initial scope described here. The concept exports a signed review result and machine-readable decision. Execution, post-change verification, and compensating rollback are future directions.
What happens when evidence is insufficient?
It remains explicitly unknown. The product should not turn missing evidence into an inferred approval. A reviewer can request changes or escalate the exact version.
What should I submit through this website?
Only broad qualification information about your automation platform, first system, proposed write pattern, current approval method, and timing. Do not submit credentials, real tickets, employee records, customer data, or policy documents.