FAQHonest answers to the questions a buying committee actually asks.
About dashboards, the AI-coding budget, vendor maturity, the Ledger methodology and the surveillance concern. A living document, refreshed from real conversations.
- Is this a dashboard?
- No. A dashboard reports what already happened. The Foresight Ledger surfaces the late-knowledge risks forming inside your delivery — signal, foresight, action, and the measured outcome — before delivery slips.
- How does Qeino sit alongside our AI-coding budget?
- AI-coding tools speed code production. Qeino measures and protects delivery certainty across the programme. The two are complementary line items, not substitutes — and the Ledger makes the distinction auditable.
- You're early. Why should we trust the platform?
- The deployment model is the trust model: air-gapped or on-prem, EU-sovereign, source-code escrow on the certification roadmap, and a CFO-signed Ledger export for every claim. Vendor-stability materials are available under NDA.
- How is the Ledger methodology defined?
- Five measured dimensions, each with a documented baseline and a documented method. The Foresight Ledger Guide sets them out in full, including your challenge rights on any figure.
- Is this surveillance of our engineers?
- No. Qeino reads programme signal, not individual behaviour. The read-access surface map in the Security Overview names what is read and what is never touched. Authority remains with your engineering leadership.