The client platform
Mythos is where an engagement meets your team: hand in what the cycle needs, watch where the month stands, and collect every deliverable when it is ready. Storage sits in your own OneDrive rather than on our servers, so the answer to where your data lives is architectural rather than a promise.
Mythos is how an engagement reaches you: what you hand in, where the cycle stands, and every deliverable when it is ready. Files are stored in your own OneDrive rather than on our servers. Data passes through; it does not move in.
Whatever the cycle needs from your side, uploaded once rather than assembled over email: travel data, hotel documents, entity changes, GSTIN updates.
Collection, extraction, reconciliation and carrier follow-up run on our side while Mythos shows you exactly where the month stands, without anyone having to ask.
Documents, register, reconciliation output, the follow-up log and the month close pack, filed into your OneDrive under a structure your team can navigate without us.
Mythos carries a separate identity because it is the part of TraCarta your team actually touches. The firm signs the work; the platform delivers it.
A plain wordmark, one accent, nothing else. The full stop is the point: a cycle is handed in, worked, delivered, and closed. Files come to rest in your OneDrive, not on our servers, so the platform is a route rather than a destination.
The question every infosec team asks is where the data lives. Storage in your own tenant is a structural answer rather than an assurance, and structure is checkable.
Deliverables are written to your OneDrive through the Microsoft Graph API. Once a cycle is delivered, our working copy is done with. We cannot lose what we do not keep.
Role based, granted per engagement, and revocable by you. Your travel data is employee data, and it is treated as such.
Mythos exists to deliver the work, not to become another system to learn, licence and administer. If it required training, we would have failed at the service.
Deliberately narrow. Everything else belongs in the engagement, not in an interface.
One upload point per cycle, so nothing depends on finding the right email thread six months later.
Collection complete, register delivered, reconciliation running, follow ups open. The month's status without a status call.
Every deliverable, every cycle, in one place, in a structure that still makes sense at audit time.
A review includes a walkthrough of the path your data takes, end to end. Your infosec team is welcome on the call.