MITHRIL · 2026-11-02
One map of Mithril products, services and platform foundations: what each does, its current scope and what must happen next.
This is a dated inventory, not a promise that every component is a managed service. Now / Next / Later describes dependency order, not launch dates. Native releases and account access have their own conditions.
Maintain public resources and qualify actual account workflows.
Complete native VPN, signed clients and one accepted service workflow before expanding.
Expand only after measured demand, qualified capabilities and operating capacity.
Desktop and standalone CLI share a native VPN controller; mobile follows the same enrollment contract. A separate Cloudflare or WireGuard app is not the target. OS consent remains required. First qualify one non-GCP region, real traffic and signed client updates within USD 100/month for pilot infrastructure. Tenant-dedicated fixed IP follows later. The current external-client setup trial does not meet this acceptance gate.
55 / 55 catalog entries
Pilot / limited scope · Next
Desktop agent workspace and Device care. Current installers do not establish the planned integrated VPN.
Next acceptance gate: Signed installers, supported-OS install/update/rollback and installed feature verification.
View scope and detailsPilot / limited scope · Next
Terminal agent workflows; the planned VPN commands must also work without a Desktop renderer.
Next acceptance gate: Standalone packaging, scoped native authority and end-to-end command verification.
View scope and detailsPilot / limited scope · Next
Android and iOS companion source. Store availability, platform features and VPN qualification are separate.
Next acceptance gate: Signed Android/iOS releases and physical-device lifecycle, connection and update QA.
View scope and detailsPlanned · Next
VPN inside Mithril Desktop or CLI, with mobile integration to follow. No separate VPN app; dedicated tenant IP is deferred.
Next acceptance gate: One qualified non-GCP egress, native enrollment/traffic/failure tests, signed distribution and a USD 100/month infrastructure ceiling.
View scope and detailsSource candidate · Next
Native storage and application-inventory work, with protection capabilities qualified individually.
Next acceptance gate: Installed OS permissions and measured behavior; no unqualified antivirus or kill-switch claims.
View scope and detailsPilot / limited scope · Now
Browser workspace for account-bound agent workflows and records.
Next acceptance gate: Keep account isolation, durable records and actual workflow acceptance current.
View scope and detailsPilot / limited scope · Now
Conversation and consultation interface with explicit usage and data-handling conditions.
Next acceptance gate: Verify real-device voice, consent, persistence and user-controlled follow-up.
View scope and detailsPilot / limited scope · Now
Editable coding samples and reviewed generation, with separate GitHub and publication authority.
Next acceptance gate: Maintain source review, execution boundaries, publishing receipts and comparable evaluation.
View scope and detailsAccount / operator access · Next
Private integration and tool catalog; public descriptions do not expose private tools or grant execution.
Next acceptance gate: Reviewed public projections, tenant/case authorization and qualified connector contracts.
View scope and detailsPublic resource · Now
Source-linked security knowledge and data exploration.
Next acceptance gate: Maintain provenance, data-use rights, freshness and query limits.
View scope and detailsPublic resource · Now
Ontology and relationship exploration over published data.
Next acceptance gate: Verify source/custody boundaries and published graph coverage.
View scope and detailsPublic resource · Now
Security scenarios, evaluation methods and measured results with explicit coverage.
Next acceptance gate: Publish only measured, reproducible comparisons; qualify new benchmarks separately.
View scope and detailsPublic resource · Now
Model information, provenance and research direction; catalog presence is not endpoint availability.
Next acceptance gate: Bind served model identity, quality, access and cost to current evidence.
View scope and detailsPublic resource · Now
Phishing, phone-safety and breach-related lookup routes with dated source limits.
Next acceptance gate: Reconcile coverage, removed sources and freshness; a match is not an attribution verdict.
View scope and detailsPhone safety lookupPublic resource · Now
Crypto, sanctions, law, enforcement, compliance, CSF2, video/IP and funding-reference routes; each retains its own data limits.
Next acceptance gate: Audit source rights and actual availability per dataset; preserve dormant and withdrawn states.
View scope and detailsPublic resource · Now
Dated breach reporting and links to original announcements.
Next acceptance gate: Source attribution, corrections, date precision and independent update read-back.
View scope and detailsPilot / limited scope · Next
Monthly service-token plans and scoping consultation; contracted work has separately agreed scope and delivery.
Next acceptance gate: Qualified enrollment, signed terms, service capacity, delivery receipts and cost controls.
View scope and detailsSource candidate · Next
Evidence-to-improvement and retest workflows for a bounded enterprise workload.
Next acceptance gate: One authorized customer/source, reviewed evidence, comparable retest and accepted workload outcome.
View scope and detailsPilot / limited scope · Next
Company-funded program preparation and account controls. A public page grants no testing scope or reward entitlement.
Next acceptance gate: Owner authorization, scoped terms, funding, tested submission/review/payment and public read-back.
View scope and detailsPublic resource · Next
Role-based investigation and evidence-handling examples; engagement and official-channel actions need their own authority.
Next acceptance gate: Case-scoped access, custody, reviewed actions and qualified recipient/channel receipts.
View scope and detailsPublic resource · Now
Guidance for preserving records and choosing next steps; users remain responsible for reports and decisions.
Next acceptance gate: Keep records private and distinguish guidance from staffed investigation or guaranteed recovery.
View scope and detailsPublic resource · Now
Self-study material and security exercises; instructor-led work requires separate scope and availability.
Next acceptance gate: Publish evaluated learning outcomes and confirm training capacity before offering dates.
View scope and detailsPublic resource · Next
Cybersecurity role and learning references, with candidate-intake limits stated separately.
Next acceptance gate: Qualified candidate intake, employer consent and actual matching outcomes.
View scope and detailsPublic resource · Now
Public learning/play experience associated with Hikari.
Next acceptance gate: Verify learning/play routes and accessibility before extending outcomes.
View scope and detailsSource candidate · Later
Planned calls with impersonation-defense research. Detection quality and production calling remain unqualified.
Next acceptance gate: Admitted detector results, processor/consent controls, real multi-device calls and a qualified release.
View scope and detailsUnder verification · Later
Community direction; the observed public root returned 404, so no community-enrollment promise is made.
Next acceptance gate: Working public route, moderation, access controls and actual participation flow.
View scope and detailsPlanned · Later
Planned expert/service matching, separate from current inquiry routes.
Next acceptance gate: Provider participation, terms, matching, delivery, disputes and payment acceptance.
View scope and detailsPublic resource · Later
Digital-twin and synthetic demonstration surface; not a production operational model.
Next acceptance gate: Qualified real inputs, simulation validity and customer-specific acceptance.
View scope and detailsUnder verification · Later
Dedicated public route retained in the site ledger; functional scope needs a current acceptance pass.
Next acceptance gate: Document the supported workflow and independently verify it before a product-availability claim.
View scope and detailsUnder verification · Later
Catalog surface with legacy source history and dataset-specific limits.
Next acceptance gate: Rights, freshness, retired-source handling and actual query acceptance.
View scope and detailsPilot / limited scope · Next
Dedicated Mithril web surface; runtime availability and permitted workflows must be verified individually.
Next acceptance gate: Current runtime, authorized account flow and evidence-backed capability coverage.
View scope and detailsPilot / limited scope · Now
Shared authenticated platform API plus explicitly public read-only endpoints.
Next acceptance gate: Maintain account scopes, schema compatibility, measured quotas and endpoint acceptance.
View scope and detailsAccount / operator access · Now
Sign-in, account administration, plans and credits under account-specific permissions.
Next acceptance gate: Fresh authentication, isolation, revocation and actual billing/ledger reconciliation.
View scope and detailsAccount / operator access · Next
Account-gated storage surface; storage access and recovery guarantees require explicit qualification.
Next acceptance gate: Owner isolation, integrity, recovery, retention and accepted file workflows.
View scope and detailsAccount / operator access · Now
Operator infrastructure, not a public customer product or open MCP endpoint.
Next acceptance gate: Preserve operator authorization, minimal projections and auditability.
View scope and detailsPublic resource · Now
Published guides, dated updates and product-help routes.
Next acceptance gate: Keep source/version references, contact ownership and availability accurate.
View scope and detailsPublic resource · Next
Published trust/reporting material with legal drafts and unapproved policies labeled separately.
Next acceptance gate: Counsel/owner review, current disclosures and tested security-reporting intake.
View scope and detailsPlanned · Later
Partnership inquiries exist; startup benefits and future events are not an active public offer.
Next acceptance gate: Approved programme terms, capacity and actual event/participant acceptance.
View scope and detailsSource candidate · Next
Organization-scoped enrollment planning and policy/action foundations. Native management and dispatch are not available yet.
Next acceptance gate: Provider registrations, native enrollment/dispatch, four-OS lifecycle evidence, privacy terms and qualified publication.
View scope and detailsSource candidate · Later
CMS and WordPress migration direction with owner-approved publishing; hosted tenant URLs remain unqualified.
Next acceptance gate: Tenant isolation, private previews, exact-host authority, media recovery and an approved production publisher.
View scope and detailsPlanned · Later
Separate, consented contact and provider-hosted verification signals for business onboarding; no general fraud score is offered.
Next acceptance gate: Lawful purpose, provider/data rights, minimized retention, calibrated evaluation and human review boundaries.
View scope and detailsPlanned · Later
Discovery of camera, sensor and physical-access security needs for Home/Office; no monitoring service is active.
Next acceptance gate: Agreed use case, consent/data policy, device feasibility and an accepted safety/operations contract.
View scope and detailsPlanned · Later
Optional isolated decoy research for explicitly approved synthetic workloads, separate from production traffic.
Next acceptance gate: Isolated ownership, workload authorization, complete evidence and reviewed operational acceptance.
View scope and detailsPlanned · Later
Source-linked transaction-monitoring and triage direction; evidence is distinct from fraud attribution.
Next acceptance gate: Permitted historical data, tested triage, measured delivery and reviewed public projections.
View scope and detailsPlanned · Later
Reviewed incident research and controlled information-sharing direction, with source and authority boundaries.
Next acceptance gate: Case-scoped lawful access, corroborated sources, recipient controls and reviewed sharing receipts.
View scope and detailsSource candidate · Next
Shared local/cloud agent-environment direction, separate from current local fleet and storage synchronization.
Next acceptance gate: Image identity, transactional state, single-writer leases, real failover and qualified remote execution.
View scope and detailsComponent; engagement separate · Now
Defined exposure-management component. Review its documented scope; this is not a managed service availability claim.
Next acceptance gate: Qualify authorized collection, complete coverage, freshness and tenant-specific operational acceptance.
View scope and detailsPlanned · Next
Gated dynamic-testing service definition; not available as a hosted service.
Next acceptance gate: Qualify explicit target scope, authenticated tests, reproducible evidence and safe execution.
View scope and detailsPlanned · Next
Gated static-analysis service definition; not available as a hosted service.
Next acceptance gate: Qualify source custody, language coverage, reproducible findings and remediation validation.
View scope and detailsPlanned · Next
Gated spear-phishing-detection service definition; not available as a hosted service.
Next acceptance gate: Qualify mail access, input custody and labeled detection results before a hosted offer.
View scope and detailsComponent; engagement separate · Now
Defined vulnerability-management component. Review its documented scope; this is not a managed service availability claim.
Next acceptance gate: Qualify tenant findings, deduplication, remediation lifecycle and accepted reports.
View scope and detailsComponent; engagement separate · Now
Defined governance component. Review its documented scope; this is not a managed service availability claim.
Next acceptance gate: Validate the organization evidence, reviewed profiles and actual customer acceptance.
View scope and detailsComponent; engagement separate · Now
Defined incident-response component. Review its documented scope; this is not a managed service availability claim.
Next acceptance gate: Keep planning outputs separate from a staffed incident response or an official notification.
View scope and detailsComponent; engagement separate · Now
Defined recovery component. Review its documented scope; this is not a managed service availability claim.
Next acceptance gate: Keep restore planning separate from an executed, verified recovery.
View scope and detailsPlanned · Next
Gated readiness-evaluation service definition; not available as a hosted service.
Next acceptance gate: Qualify authorized inventory/evidence, reviewed improvements and comparable retests.
View scope and detailsReconciled from the Fund resource manifest, live Cloudflare host/DNS inventory and anonymous root requests on the review date. HTTP 200 proves a response, not functional or commercial readiness. Public root checks used no account credentials or authentication bypass. Retired, planned and mail-only names are included separately; public DNS is not an availability promise.
| Domain | Role | Observed state |
|---|---|---|
| admin.mithril.fund | Operator administration | auth-required |
| analysis.mithril.fund | Security analysis and evaluation | http-200 |
| api.mithril.fund | Platform API | http-200 |
| app.mithril.fund | Browser workspace | http-200 |
| auth.mithril.fund | Account sign-in | sign-in |
| blog.mithril.fund | Dated articles and product notes | http-200 |
| bounty.mithril.fund | Company Bounty surface | http-200 |
| breach.mithril.fund | Breach Calendar | http-200 |
| code.mithril.fund | Code / System One Coding | http-200 |
| console.mithril.fund | Account, plans and credits | sign-in |
| crm-mcp.mithril.fund | Operator CRM/MCP endpoint | auth-required |
| docs.mithril.fund | Documentation | http-200 |
| dojo.mithril.fund | Dojo learning | http-200 |
| graph.mithril.fund | Graph exploration | http-200 |
| guild.mithril.fund | Community route under verification | http-404 |
| hikari.mithril.fund | Hikari roles and learning | http-200 |
| knowledge.mithril.fund | Security knowledge | http-200 |
| kyber.mithril.fund | Kyber | http-200 |
| ludo.mithril.fund | Hikari Baito Ludo | http-200 |
| mithril.fund | Public website, products, services and roadmap | http-200 |
| models.mithril.fund | Model catalog and research | http-200 |
| storage.mithril.fund | Account-gated storage | sign-in |
| suit.mithril.fund | Retained Suit surface | http-200 |
| support.mithril.fund | Product guidance and contact | http-200 |
| talk.mithril.fund | Sam / Talk | http-200 |
| twin.mithril.fund | Twin / Polaris demonstration | http-200 |
| vpn.mithril.fund | Retained DNS for retired GCP VPN pilot | retained |
| www.mithril.fund | Alias redirect to the public website | http-200 |
| yabai.mithril.fund | Yabai catalog | http-200 |
| apps.mithril.fund | Retired Apps domain; replacement is App extensions | retired |
| briefing.mithril.fund | Planned Briefing hostname; no live service qualified | planned |
| cf-bounce.mail.mithril.fund | Mail return-path routing; not a web product | |
| mail.mail.mithril.fund | Mail routing configuration; not a web product | |
| mail.mithril.fund | Mail transport; not a web product | |
| *.sites.mithril.love | Planned MithrilPress tenant URL pattern; exact-host ownership and publication unqualified | planned |
These are migration/routing states from the retained site ledger, not the current availability labels above. A dormant historical entry can now have a different public product; names without a hostname do not imply a registered domain.
%20scale(.9)%22%3E%3Cpath%20d%3D%22M12%201.25%206.25%207.25%2012%209.5z%22%20fill%3D%22%239db7f9%22%20fill-opacity%3D%22.42%22%2F%3E%3Cpath%20d%3D%22M6.25%207.25%2012%209.5V19l-5.75-2.25z%22%20fill%3D%22%239db7f9%22%20fill-opacity%3D%22.16%22%2F%3E%3Cg%20fill%3D%22none%22%20stroke%3D%22%239db7f9%22%20stroke-linejoin%3D%22round%22%20stroke-linecap%3D%22round%22%3E%3Cpath%20d%3D%22M12%201.25%2017.75%207.25v9.5L12%2022.75l-5.75-6V7.25z%22%20stroke-width%3D%221.5%22%2F%3E%3Cpath%20d%3D%22M12%201.25v21.5M6.25%207.25%2012%209.5l5.75-2.25M6.25%2016.75%2012%2019l5.75-2.25%22%20stroke-width%3D%221.1%22%20stroke-opacity%3D%22.85%22%2F%3E%3C%2Fg%3E%3Cpath%20d%3D%22M20.25%201.5l.45%201.3%201.3.45-1.3.45-.45%201.3-.45-1.3-1.3-.45%201.3-.45z%22%20fill%3D%22%239db7f9%22%2F%3E%3C%2Fg%3E%3C%2Fsvg%3E){kind=small}
account · dormant · No hostname assigned in ledgeradmin · active · admin.mithril.fundapps · dormant · apps.mithril.fundbilling · dormant · /billingblog · active · blog.mithril.fundchat · dormant · /chatcompliance · active · /compliancecrypto · dormant · No hostname assigned in ledgercsf2 · active · /csf2dashboard · active · console.mithril.funddata · paused · No hostname assigned in ledgerdm2 · active · graph.mithril.funddocs · active · docs.mithril.fundenforcement · dormant · No hostname assigned in ledgerfake_report · dormant · /fake-reportidentity · dormant · /identityknowledge · active · knowledge.mithril.fundlaw · dormant · No hostname assigned in ledgermodels · dormant · No hostname assigned in ledgerorgbrain · dormant · /orgbrainpwned · dormant · No hostname assigned in ledgerrecords · dormant · /security/recordsrequests · dormant · No hostname assigned in ledgerresearch · dormant · /researchsanctions · dormant · No hostname assigned in ledgersandbox · dormant · app.mithril.fundsecure · dormant · /securesecurity · dormant · No hostname assigned in ledgersecurity_services · active · /security/servicessousa · dormant · /sousastorage · dormant · storage.mithril.fundsuit · active · suit.mithril.fundsupport · active · support.mithril.fundtrust · dormant · No hostname assigned in ledgertwin · active · twin.mithril.fundvc · dormant · No hostname assigned in ledgervideoip · dormant · No hostname assigned in ledgeryabai · dormant · yabai.mithril.fundyabai_crypto · dormant · No hostname assigned in ledgeryabai_waterplum · dormant · No hostname assigned in ledger