Janusly
GitHubRequest access
Self-hosted · one executable · your PostgreSQL

The AI operator for your business workflows.

Janusly turns intent into a reviewable workflow, checks declared business outcomes, and brings failures into governed recovery. Technical completion is not the same as a verified result. One Go binary, on your infrastructure.

Request accessSee the Recovery Center

Docker image or a single binary. PostgreSQL 18. No control plane to rent.

/#/runs/dlq
Janusly Recovery queue with two open failures and one selected
The Recovery queue: every failed step, clustered by cause, with the evidence for a governed decision.
Why Janusly

Design, run, verify and recover in one place.

Design, run, recover and operate live in the same runtime, so a failure on Tuesday is a workflow change on Wednesday, with the evidence attached.

Design

Describe the outcome. AI Studio compiles an intent brief into a workflow you can read, with every tool, credential and approval named before anything runs.

Run

Every step is a row in your PostgreSQL. Idempotent starts, bounded workers, LISTEN/NOTIFY wake-ups and polling as the fallback, so nothing depends on a broker you have to babysit.

Recover

Failures are clustered by cause. Replay one, run a campaign over the cluster, or let auto-healing propose a fix that is validated on one sample first, with external writes suppressed. Recovery contracts carry fixtures that must pass before a rollout.

Operate

AI spend budgets per workflow, alert policies, a circuit breaker that pauses every entry point until you resume, public status pages, and metrics and traces out of the box.

Product

What an operator sees on a bad morning.

Three surfaces, one runtime, no diagrams: every screen below is the product over a seeded organization.

Janusly Recovery Center: the failure queue with the automation panel open
Recovery CenterThe queue of failed steps, the cluster they belong to, replay campaigns and the auto-healing proposals waiting for a decision.
Janusly AI Studio: a compiled intent brief and a workflow proposal
AI StudioAn intent brief compiled from a sentence, the capabilities it binds to, and a proposal you read before it becomes a draft.
Janusly Home: the Recovery Center landing with health ring and next actions
HomeThe operator landing: outcome posture, the longest downtime still counting, and the next action, computed from your runs.
Access

Evaluate Janusly on your infrastructure.

Review the product and its evidence first. Use requires prior written permission; contact the copyright holder about licensing and deployment.

Discuss access on GitHub
FAQ

Questions operators ask first.

Do I need Kubernetes?
No. One executable serves the API, the web app, the workers and the maintenance loops, and PostgreSQL 18 is the only dependency. A container image build is part of every release.
Where does my data live?
Workflow state and evidence live in your PostgreSQL. Configured integrations and AI providers receive the data needed for their calls. Credentials are encrypted at rest and withheld from lists, logs and error payloads; authorized provider calls use them.
What happens when the AI provider is down or over budget?
AI calls return a deterministic fallback envelope when unavailable or over budget. A fallback is not proof that the business objective was met: configured outcome checks can still reject it or quarantine downstream work.
Can it use my existing tools and agents?
Yes. Janusly is an MCP client for your tools and an MCP server that exposes your workflows to the agents you already run.
Is it available in Spanish?
The product ships in English and Spanish, and so does this site.

Start with one workflow you can verify.

Review the provider-free walkthrough and its evidence limits before authorizing actions against a real service.

Request accessRead the docs