Frequently asked questions

A tool to see, understand and audit the work of coding agents. The open edition gathers every agent of one person in one inbox and one campus. İZAN Server brings the same picture to the company: city view, reports, approval by role and an audit log.

Claude Code is supported in full, through its hooks and its own logs. GitHub Copilot CLI, OpenAI Codex and Gemini CLI are followed read-only from their logs and show on their own floors of the campus. İZAN Server’s hosted runners use the company’s own key through the Anthropic API, Amazon Bedrock or Google Vertex.

Nowhere. The bridge never calls a model and never stores command text or file contents. A bridge enrolled with a server sends only numbers, states, gate decisions and keyed ids. Prompts, transcripts, titles, folder and project names stay on the machine. Every record that can be sent is listed in a published schema.

No. A bridge that is not enrolled makes no request to any server: no timer, no outbox, no telemetry. The open core never phones home and never checks a licence.

Yes. The same product runs on your own server, even in an air-gapped network. The licence file is checked offline on the server; no network access is needed to install or to renew. Lyconiq runs the cloud edition from the same image.

Yes. OIDC (with PKCE) works with Entra ID, Okta, Google Workspace, Keycloak, Ping, ADFS, Auth0 and Authentik, and SAML 2.0 is supported. Access follows the scope tree, company → department → team → person, with admin, lead and member roles at each scope.

In the open edition, in the operating system’s secret store or environment variables; the bridge stores none. In İZAN Server the vault holds scoped keys per connection: KMS or the company’s own secret store, with short-lived grants and an audit trail.

Every entry is chained to the one before; a changed entry shows up when the chain is verified. The log exports as JSONL or CSV and verifies offline. It flows to your SIEM over syslog with TLS (RFC 5425) or a signed HTTPS webhook.

The open edition is MIT-licensed and free. İZAN Server is licensed per active developer (Team $12, Business $24, Enterprise $36; monthly list price, billed yearly). The licence is a signed file checked offline on the server. Details: Pricing.

One team, 6 weeks, free, on your own server. The first week sets a baseline; in the last week you look at the same measures and decide to continue or stop. Pilot page.

One virtual machine, an app registration in your identity provider, a security reviewer, and the team’s time: the setup day and 30 minutes a week. We ask for no access to your data sources.

Two options. Continue with a seat licence per active developer, or stop: the audit log and reports are exported and the open edition stays with the developers. No lock-in.

Open core: the bridge, the campus, the process engine and the station are open under the MIT licence. The company layer (İZAN Server) is commercial and uses the open core as a dependency, never as a fork. Code: github.com/Lyconiq/izan.

macOS, Linux and Windows. Install with npx @lyconiq/izan; it sets the bridge up as a service with launchd, systemd or Task Scheduler.

Team is for seeing the teams: city view, reports, company sign-in, audit log. Business is for governing the work: server gates with role approval, custom roles and constraints, Jira, Azure DevOps and Linear, the vault, SAML and SCIM. Enterprise adds SIEM forwarding, an external decision point (OPA), the process catalogue, Studio, hosted runners and air-gapped installation. Comparison.