agent · ai agents platform

Orloj

orloj.devevidence retrieved Aug 1, 2026view as JSON all ai agents platform entries 93 alternatives

Indexed12 or more fields evidenced; not yet scored by a human against the rubric

25 fields evidenced · 30 with no public information. Every value below links to the document it came from and the date we checked it.

25 of them are quoted but not yet interpreted: we hold the source sentence and the date we read it, but nobody has written the answer to the question yet. Those rows show the quote and say so rather than repeating it back as an answer. Why these exist

4 of those are flagged for review: our own check found language in the cited source that may address the field. An editor has not adjudicated them yet.

1 absence has been read back against the source by an editor and confirmed.

Also appears in

AI agents and vendors that state SOC 2 AI agents that support the Model Context Protocol AI agents and vendors that state HIPAA compliance AI agents and vendors that reference the EU AI Act AI agents that publish an uptime SLA

Trust gap

How this is scored

These scores are automated. A 1 or 2 counts how many fields this entry answers with a citation — not what those answers say. A 0 means every field for that dimension is recorded as undisclosed and none of the pages we captured mentions it. No one has scored this entry against the rubric yet.

Runtime governance

1/3 auto

Are scope, spend, and authority enforced while the agent runs?

Scored from 1 evidenced field(s): runtime_governance. Automated score; capped at 2 pending review.

Counts Runtime governance, each cited below.

This score counts Permission scopes as undisclosed, and that absence is flagged for review — the cited source may address it. If so, this score is too low. How we check absences

Audit trail

1/3 auto

Is there a tamper-evident record of what it actually did?

Scored from 1 evidenced field(s): audit_trail. Automated score; capped at 2 pending review.

Counts Audit trail, each cited below.

Compliance

2/3 auto

Are compliance obligations attached per engagement?

Scored from 2 evidenced field(s): compliance_certs, regulatory_alignment. Automated score; capped at 2 pending review.

Counts Compliance certifications and Regulatory alignment, each cited below.

Outcome settlement

unscored

Does payment depend on a verified result?

Insurance & indemnity

unscored

Can the deployment be insured, and is the customer indemnified?

Assurance

Insurance available: no public information
orloj.dev · checked Aug 1, 2026 · source did not state this
Insurance carriers: no public information
orloj.dev · checked Aug 1, 2026 · source did not state this
Coverage limits: no public information
orloj.dev · checked Aug 1, 2026 · absence verified against this source
Indemnification: no public information
orloj.dev · checked Aug 1, 2026 · source did not state this
Liability cap: no public information
orloj.dev · checked Aug 1, 2026 · source did not state this
Audit trail: not yet interpreted
“Full task trace and message lifecycle logging”
orloj.dev · checked Aug 1, 2026
Tamper-evident log: no public information
orloj.dev · checked Aug 1, 2026 · source did not state this
Explainability: not yet interpreted
“Fail-closed governance at the execution layer”
orloj.dev · checked Aug 1, 2026
Runtime governance: not yet interpreted
“Governance is enforced at the execution layer”
orloj.dev · checked Aug 1, 2026
Permission scopes: no public information
Flagged for review — the source below contains language that may address this field. Not yet checked by an editor. How we check absences
orloj.dev · checked Aug 1, 2026
Compliance certifications: not yet interpreted
“The structured audit trail is designed to support compliance workflows for frameworks like HIPAA, SOC 2, and the EU AI Act.”
orloj.dev · checked Aug 1, 2026
Regulatory alignment: not yet interpreted
“The structured audit trail is designed to support compliance workflows for frameworks like HIPAA, SOC 2, and the EU AI Act.”
orloj.dev · checked Aug 1, 2026
Outcome-based pricing: no public information
orloj.dev · checked Aug 1, 2026 · source did not state this
Settlement mechanism: no public information
orloj.dev · checked Aug 1, 2026 · source did not state this
Dispute process: no public information
orloj.dev · checked Aug 1, 2026 · source did not state this
SLA terms: not yet interpreted
“Custom SLAs and uptime guarantees”
orloj.dev · checked Aug 1, 2026
Evaluation coverage: no public information
orloj.dev · checked Aug 1, 2026 · source did not state this

Agency

Autonomy level: no public information
orloj.dev · checked Aug 1, 2026 · source did not state this
Human oversight: not yet interpreted
“Governance is enforced at the execution layer”
orloj.dev · checked Aug 1, 2026
Goal complexity: not yet interpreted
“Declarative YAML graphs with fan-out and join gates”
orloj.dev · checked Aug 1, 2026
Action space: no public information
orloj.dev · checked Aug 1, 2026 · source did not state this
Operating environment: not yet interpreted
“Tool Runtime sandboxed, container, WASM”
orloj.dev · checked Aug 1, 2026
Initiative: not yet interpreted
“Orloj schedules, executes, and governs them”
orloj.dev · checked Aug 1, 2026

Safety

Safety evaluations: no public information
orloj.dev · checked Aug 1, 2026 · source did not state this
Red teaming: no public information
orloj.dev · checked Aug 1, 2026 · source did not state this
Safety policy: not yet interpreted
“Fail-closed governance at the execution layer”
orloj.dev · checked Aug 1, 2026
Usage restrictions: not yet interpreted
“blocked_tools: - filesystem_delete”
orloj.dev · checked Aug 1, 2026
Model or system card: no public information
orloj.dev · checked Aug 1, 2026 · source did not state this
Incident reporting: not yet interpreted
“Full task trace and message lifecycle logging”
orloj.dev · checked Aug 1, 2026
Third-party evaluations: no public information
orloj.dev · checked Aug 1, 2026 · source did not state this
Data handling: not yet interpreted
“Full task trace and message lifecycle logging”
orloj.dev · checked Aug 1, 2026

Practicality

Pricing model: no public information
Flagged for review — the source below contains language that may address this field. Not yet checked by an editor. How we check absences
orloj.dev · checked Aug 1, 2026
Price point: no public information
orloj.dev · checked Aug 1, 2026 · source did not state this
Availability: not yet interpreted
“Orloj v0.19.0 is live.”
orloj.dev · checked Aug 1, 2026
Deployment options: no public information
Flagged for review — the source below contains language that may address this field. Not yet checked by an editor. How we check absences
orloj.dev · checked Aug 1, 2026
Integrations: not yet interpreted
“MCP tool integration”
orloj.dev · checked Aug 1, 2026
Supported regions: no public information
orloj.dev · checked Aug 1, 2026 · source did not state this
Support model: no public information
Flagged for review — the source below contains language that may address this field. Not yet checked by an editor. How we check absences
orloj.dev · checked Aug 1, 2026

Foundation models

Base models: no public information
orloj.dev · checked Aug 1, 2026 · source did not state this
Model provider: not yet interpreted
“Model Gateway OpenAI, Anthropic, Ollama”
orloj.dev · checked Aug 1, 2026
Model swappable: not yet interpreted
“model_ref: openai-default”
orloj.dev · checked Aug 1, 2026
Open weights: not yet interpreted
“Orloj is Apache 2.0 licensed and developed publicly on GitHub.”
orloj.dev · checked Aug 1, 2026
Fine-tuning: no public information
orloj.dev · checked Aug 1, 2026 · source did not state this
Context window: no public information
orloj.dev · checked Aug 1, 2026 · source did not state this

Ecosystem

Protocols supported: not yet interpreted
“MCP tool integration”
orloj.dev · checked Aug 1, 2026
Tool use: not yet interpreted
“Agents call tools they should not touch. Tool permissions enforced at execution time.”
orloj.dev · checked Aug 1, 2026
Multi-agent: not yet interpreted
“Orloj is an open-source orchestration runtime for multi-agent AI systems.”
orloj.dev · checked Aug 1, 2026
API access: not yet interpreted
“Server orlojd API Server REST, watch, web console”
orloj.dev · checked Aug 1, 2026
Open source: not yet interpreted
“Orloj is Apache 2.0 licensed”
orloj.dev · checked Aug 1, 2026
Marketplace presence: no public information
orloj.dev · checked Aug 1, 2026 · source did not state this

Impact

User base: no public information
orloj.dev · checked Aug 1, 2026 · source did not state this
Deployment scale: not yet interpreted
“Deploy on your own infrastructure with no limits. Unlimited agents and workflows”
orloj.dev · checked Aug 1, 2026
Target sectors: no public information
orloj.dev · checked Aug 1, 2026 · source did not state this
High-risk domains: no public information
orloj.dev · checked Aug 1, 2026 · source did not state this
Documented incidents: no public information
orloj.dev · checked Aug 1, 2026 · source did not state this