Your data: locked down, never lost, always yours.
Yolm runs your business as one system on one live database. That means one place to secure, one permission model, and one audit trail — not a dozen copies to track down. Here is how it is protected, what is in place today, and what comes next.
At a glance
Every copy of your data is one more thing to protect.
Most businesses run on many applications, exports, and spreadsheets, each with its own logins, its own permissions, and its own copy of the data. Yolm removes the copies instead of adding another security tool on top of them.
Data in many places
Customer, job, and financial data is copied between applications, reporting tools, and spreadsheets on laptops.
One live database
Standard and company-specific applications work from the same encrypted database. There is nothing to export to keep reports current.
Many permission models
Each tool has its own users and roles. Offboarding someone means remembering every system they touched.
One set of roles
Roles and permissions are defined once and enforced in every application, API, and AI agent. Disable a user once and every door closes.
Gaps in the trail
When data moves between systems, the history of who changed what is split across logs that do not line up.
One audit trail
Every change is recorded with who made it and when, in the same database the business runs on.
The core of Yolm is written in Rust.
A whole class of attacks is designed out.
Memory-safety bugs — buffer overflows, use-after-free errors, and data races — are behind a large share of serious security vulnerabilities in systems software. Rust prevents these bugs when the code is compiled, before it ever runs.
Database, runtime, and compiler
The Yolm database engine, the runtime that serves your applications, the compiler, and the edge software are written in Rust.
Safer by construction
Rust checks memory access and concurrency at compile time, so these mistakes are caught while the software is built rather than discovered in production.
Stable under load
The same guarantees that close security holes also guard against crashes and memory corruption, which matters for a system your whole business runs on.
Encrypted in flight. Encrypted at rest. Built in, not bolted on.
Encryption is part of how the Yolm database stores and moves data. There is no setting to forget and no unencrypted mode.
TLS 1.3 in transit
Browsers connect over TLS 1.3. Traffic from our edge network to our servers is TLS 1.3 only, and our servers accept connections from that edge network alone.
AES-256-GCM at rest
Every data file, write-ahead log, and transaction batch is encrypted with AES-256-GCM, using AWS-LC, the cryptography library maintained by AWS.
A separate key for every system
Each customer system has its own 256-bit key. Keys are derived when needed, held only in memory, and never written to disk. Master secrets rotate quarterly, and immediately if compromise is suspected.
A second layer from AWS
Underneath, storage and disks are also encrypted with AWS Key Management Service keys that AWS rotates automatically.
Sensitive fields encrypted again
Integration credentials and the access tokens for connected email, calendar, and meeting accounts are encrypted a second time at the field level.
Signed releases
Every release is cryptographically signed, and servers verify the signature before they run it.
Your identity provider. Your roles. Enforced everywhere.
Access control lives in the system itself, so every screen, report, API, and AI agent checks the same permissions.
Single sign-on
Connect your SAML identity provider so people sign in with the accounts IT already manages. Google sign-in, email and password, and passwordless one-time codes are also available.
Two-factor authentication
Require a second factor from an authenticator app (TOTP), email, or SMS, set per application — stricter for finance and admin, lighter for frontline teams.
Brute-force protection
One-time codes are stored only as hashes and are rate-limited — by default, three attempts per ten minutes.
Role-based permissions
Named permissions, roles that inherit from other roles, and explicit denials. HR can assign roles without opening Accounting, and admin roles are protected from ordinary managers.
Support access with limits
Acting as another user requires a permission, a written reason, and a time limit of one hour or less. It can never grant more access than the person doing it already holds.
AI signs in like an employee
Yolm Spark and connected AI assistants use the person's own login and permissions, after explicit consent. Permissions are checked live on every action, so revoking access or changing a role takes effect on the next request.
Browsers never send database queries. Every query is compiled and type-checked before the system goes live, and a browser can only ask for what the application defines. Every application also ships with a Content-Security-Policy and clickjacking protection by default.
Your data does not train our AI.
AI in Yolm works inside your system under your permissions. Which model sees your data, and on what terms, is a choice you can see and control.
Yolm does not use your data for AI
Your business data is never used by Yolm to train or improve AI models.
The model's terms apply
When AI answers a question, the data it needs goes to the AI model in use, under that provider's data terms. We will tell you which models your system uses.
Bring your own AI provider
Through the Model Context Protocol (MCP), your team can connect the AI assistant and provider your company has already approved, under your own agreement, with each person's own permissions.
Who changed what, and when. Every time.
The audit trail is not a separate logging product. It is the way the Yolm database records every change.
Every change recorded
Each transaction records the user or automated process that made it and the time. Inserts, updates, deletes, and restores are all part of the log.
History stays with the record
Approvals, files, revisions, and exceptions stay attached to the work they belong to, so an auditor does not have to piece them together.
Platform security events
Unauthorized access attempts, secret rotations, access-policy changes, and every operator action are logged with the person responsible, kept 365 days and archived beyond that.
Locked down at every layer.
Yolm runs on Amazon Web Services, with Cloudflare in front. The infrastructure is defined as code and reviewed like code.
Least-privilege IAM
Each service's AWS IAM role can reach only the specific storage, tables, and secrets it needs. No wildcard permissions, and every access-policy change is code-reviewed.
No remote shell
Servers run a read-only, hardened operating system image with SSH and remote-command agents disabled. Updates replace the whole image instead of patching a live server.
Protected edge
Cloudflare's network sits in front of every system with a managed web application firewall, rate limiting, and bot management. Our servers refuse traffic that does not come through it.
Secrets kept out of code
Credentials live in AWS Secrets Manager and are fetched by each server's own IAM role at startup. No long-lived credentials are baked into images.
Dependencies checked on every build
Every change to the platform is scanned against known-vulnerability databases, and a known vulnerability fails the build.
Monitored around the clock
Automated health checks run every minute. If a server stops responding for two minutes, the team is alerted, and alerts escalate automatically.
Your system is its own system.
Not a tenant ID in a shared database.
Yolm has no shared multi-tenant database. Each customer system gets its own production database, its own encryption key, its own storage area, and its own CPU and memory limits, so one busy system can't slow down another.
A separate instance per site, if you want it
Plants, offices, subsidiaries, or legal entities that need a hard boundary can each run as a separate system with its own database, key, and users. IT can bring them on one at a time.
Hosted in the United States
Customer data lives in AWS US East (Ohio) and US West (Oregon). Each system runs in the region closest to you and fails over to the other.
Built to add regions
The platform is designed around pairs of regions. Where your data must live is a hosting decision, not a rebuild.
Export everything, anytime
It's your data. You can export the whole database in Parquet, an open standard format that analytics tools and data platforms read directly, with a manifest describing every table's schema.
Who at Yolm can see your data
Only Yolm operations staff can reach data across customer systems. Developers — yours, ours, or a partner's — reach a system's data only through Yolm Forge, and only on systems where they have been granted permission.
Deleted when you leave
Export everything first. After your contract ends, your data is deleted within two months.
Three safeguards
against losing data.
Three independent layers stand between your business and lost data, each kept in a different way.
1. Every change, kept in the log
Every committed change is written to a write-ahead log, and we typically keep most of that history. It records how your data got to where it is, and the database can be rebuilt by replaying it.
2. Snapshots, kept for two months
Snapshots of your data are taken, typically every day, and every snapshot is kept for at least two months.
3. Stored on Amazon S3
Database data lives in Amazon S3, which AWS designs for 99.999999999% (eleven nines) durability, and is replicated to a second AWS region.
No loss on hardware failure
A write is confirmed only once it is stored durably. If a server or disk fails, committed data is not lost, and a replacement server is typically serving in two to five minutes.
A second region, always current
In a full regional outage, the design targets at most 30 minutes of data at risk and recovery within 30 minutes.
Backups nobody can erase
Stored data is versioned and locked in compliance mode for two months. Not an attacker, not an administrator, not Yolm can alter or delete it in that window.
Restores that have been tested
We have run restore drills from backup, following documented recovery runbooks.
Where we are today. Plainly.
A security review goes better with facts than with badges. This is what is in place today and what comes next.
Encryption in transit and at rest
TLS 1.3 on browser traffic and on every connection to our servers. AES-256-GCM on all stored business data, with a separate key for each customer system.
SSO, two-factor authentication, role-based permissions
SAML single sign-on, authenticator-app, email, or SMS second factor, and role-based permissions enforced on every application and action.
Security event logging
Access, secret-rotation, access-policy, and operator events go to a dedicated security log, retained for 365 days and archived beyond that.
Backups and recovery
Three independent safeguards against data loss, continuous replication to a second AWS region, and locked backups that cannot be altered or deleted. Restores from backup have been tested in drills.
Full data export
The whole database can be exported in Parquet, an open standard format, with a manifest describing every table's schema.
Designed for SOC 2
Encryption, access control, event logging, and change management were designed around the SOC 2 Trust Services Criteria.
Additional hosting regions
Today, customer data is hosted in the United States. The platform is built on pairs of regions, so a new region does not change how your system works.
Report a security issue
Found a vulnerability? Email security@yolm.ai with enough detail to reproduce it, and please give us a chance to fix it before disclosing it publicly.
Bring us your
security questionnaire.
We would rather answer the hard questions before the project starts. Send your questionnaire or book a call with the people who built the platform.