Local execution
Core automation is designed to run on the Windows computer where TessNode is installed.
Security
Automation without sending your workflow to the cloud.
TessNode is designed around local execution. This page separates current design intent from controls that are still being verified for release.
Workflow storage
Workflow definitions are designed for local storage. Final storage paths and protection guidance will be documented after release testing.
Network behavior
Core workflow execution does not require uploading workflow logic to a TessNode cloud account.
Update security
Update delivery, integrity checks, and release channels will be documented before public release.
Code signing
Code-signing status will be published with the production installer. No unverified signing claim is made here.
Data collection
TessNode is being designed without advertising. Any operational telemetry will be documented before release.
Credential handling
Avoid placing secrets directly inside workflow text. Credential-handling guidance will be included in security documentation.
Third-party dependencies
Production documentation will identify material third-party runtime dependencies and update practices.
Vulnerability reporting
Security reports can be submitted through the security documentation request path while a dedicated process is finalized.
Enterprise review
Business evaluators can request current architecture, deployment, and security information.
No certification claims.
Request Security DocumentationTessNode does not claim SOC 2, ISO 27001, HIPAA certification, or GDPR certification. Organizations can request the documentation that is currently available for review.