Contextus FAQ
Clear answers about Contextus, plans, and billing.
Contextus is the control plane for AI agent actions. This page explains the product, governance, proof, data handling, and pricing.
Product basics
What Contextus is, what it is not, and how the compile layer fits the launch story.
What does Contextus do?
Contextus helps teams govern AI agent workflows. It compiles the right context before an agent acts, applies policy to risky actions, requires approvals when needed, evaluates outputs, and keeps audit-ready proof.
Is Contextus just a context compression tool?
No. Compression is one capability inside the Compile layer. The broader product is a control plane for agent context, actions, approvals, evals, and audit trails.
What is SitEmb?
SitEmb is Contextus’s situation-aware context ranking engine. It helps select the files, docs, policies, and task history that matter for the current agent task, while reducing noisy, stale, or unrelated context. In plain terms, it helps agents stay on task instead of drowning in a bloated prompt.
What problem does Contextus solve?
AI agents are moving from chat to action. They can write code, call tools, access systems, and make decisions. Contextus helps teams control what agents see, what they can do, who approves risky steps, and how outcomes are reviewed.
Who is Contextus for?
AI engineering teams shipping agent workflows, platform teams defining policies and approvals, and developer-tool teams embedding agents into IDEs, MCP, CI, or custom environments.
Governance and approvals
How Action Control, policies, and Agent Passports turn agent activity into reviewable decisions.
What is Action Control?
Action Control is the approval and audit layer for agent tool use. It checks requested actions against policy, pauses risky actions, and records decisions in the audit trail.
What counts as a risky action?
Examples include writing files, deleting data, sending messages, making network calls, accessing credentials, running code, or changing configuration.
Can Contextus block an action?
Yes. Contextus can allow, ask for approval, deny, or redact information depending on policy and risk level.
What is Agent Passport?
Agent Passport identifies which agent is acting, who it acts on behalf of, what it is allowed to do, and when human approval is required.
Proof and evals
How Contextus turns approvals, audit logs, and evals into evidence your team can actually review.
What does “prove” mean?
Proof means keeping reviewable evidence: what context was used, which action was requested, which policy applied, who approved it, and what the evaluation result showed.
Are proof exports compliance documents?
No. They are audit-ready records that can support internal review, security workflows, and procurement conversations. They are not a certification by themselves.
Data and privacy
How Contextus handles your code, your data, and how it can be deployed.
Does Contextus see my source code?
For hosted workflows, Contextus processes the context you send through the API or connected tools. For local workflows, teams can keep more processing local depending on setup. The product can be configured based on the team’s security needs.
Does Contextus train models on my data?
No. Customer data is processed to provide the service and is not used to train models.
Can I self-host Contextus?
Self-hosted and private deployment options are planned for larger teams. Contact us to discuss enterprise deployment.
Plans and pricing
What the plans mean, what buyers get at each level, and where billing belongs.
What is personal audit history?
Builder includes a personal view of approvals, policy outcomes, and recent workflow activity so individual developers can review what happened without a shared team workspace.
How do Team approvals work?
Team adds shared approval workflows for risky tool actions, plus audit export and role-based access so reviews and escalations do not live in one person’s account.
Can I change plans anytime?
Yes. You can upgrade or downgrade as your rollout changes. In-app billing handles plan updates, and pricing changes are prorated when applicable.
Why is Team the recommended plan?
Contextus shines when approvals, audit export, and shared governance run across more than one person. Builder is great for self-serve developers, but Team better matches how organizations adopt governed agents.
Where do I manage billing after signup?
Billing belongs in the Contextus dashboard, not on the Coreledger studio homepage. The public pricing page explains plan choices, and the dashboard handles plan changes, invoices, and billing portal actions.
Do I need a team plan to get value?
No. Free and Builder are designed to let developers try the compile and governance loop on personal workflows. Team becomes the right move when approvals, audit export, and shared governance matter.
Need a next step?
Keep public pricing public, and billing in the product.
Prospects should compare plans before signup. Customers should manage plans, invoices, and billing changes inside the Contextus dashboard after sign-in.