Esacode

Security

Your data, your models, your compute

EsaSim is designed so that the most sensitive things you have, sensor data and trained models, can stay on workers you control. This page explains how.

Outbound-only workers

Workers open an HTTPS connection to esacode.com and poll for work. There are no inbound ports to open, and a worker can be revoked from the dashboard at once.

Data stays local by default

Jobs read inputs from the worker’s folder and write outputs there. The website stores job metadata, logs and an index of outputs; files are uploaded only when a preset or block is set to do so. For folders a worker shares as data, EsaSim keeps the file list, checksums and small previews, never the files.

Contained execution

On your computers the worker runs as a low-privilege service account and each task in its own folder with a time limit. Nothing from the server is passed to a shell. Blueprint blocks run on a worker only if its owner turns on Run code from projects, with the worker’s Python or in a Docker container per block. Shared GPU servers run each job in a container limited to its compute unit’s GPUs, memory and disk.

Shared folders, read in place

Only the folders listed in a worker’s settings can be indexed or read, and only inside them: paths with “..” are refused and symbolic links are not followed. Blocks write only in folders marked as writable, and in Docker shared folders are mounted read-only otherwise.

Views in a sandbox

Charts, tables and the 3D view run in a sandboxed frame in your browser, without network access and without your session. They receive only the files of the run they show.

Accounts

Passwords hashed with Argon2id (bcrypt where the server lacks it), two-factor sign-in with authenticator apps, session list with remote sign-out, and lockout after repeated failed attempts.

Organization controls

Require 2FA for every member, restrict access to IP ranges, set session timeouts, and limit features and GPUs per member.

Audit log

Membership, role, permission, security and billing changes are recorded with who, when and from where, and can be exported as CSV.

Secrets

Tokens are stored as keyed hashes and shown once. Provider credentials and API keys pasted in blocks are encrypted at rest with AES-256-GCM, never shown again, and sent only to the worker that runs the block, as environment variables. Calls to EsaSim models use a token valid only while the task runs.

Payments

Card details are handled by Stripe and never reach EsaSim servers.

Report a vulnerability

If you find a security issue, email security@esacode.com with the steps to reproduce it. Please give us reasonable time to fix it before disclosing it publicly. We do not take legal action against good-faith research.

Formal certifications are not in place yet. If your organization needs a security questionnaire answered, contact us.