Simprint

Desktop workspace for browser environments, proxy resources, and automation workflows.

👉 Join the Simprint Community Join now for updates, questions, and contributor discussions. 👇 Pick a group below

English | 简体中文

---

Introduction

Simprint is a local-first desktop workspace for browser-driven operations, designed to organize browser profiles, proxy resources, automation flows, and local runtime capabilities in one place.

It is intended for individuals and teams that need to maintain multiple browser work environments over time, including scenarios such as cross-border operations, account management, automated task execution, and shared resource coordination. With a unified desktop entry point, Simprint helps manage environment lifecycles more consistently, connect external resources, and build reusable workflows around daily operations.

Core business data is stored on the local machine by default, and normal desktop use and development can be completed locally.

Why Simprint?

Most browser automation and browser workspace products are still shaped by a few recurring limitations:

• Closed-source products that hide implementation details and reduce long-term trust.
• Cloud-only products that force operational workflows and sensitive data into third-party infrastructure.
• Anti-user product decisions that restrict ownership, portability, and control over browser environments.
• Rigid systems that are difficult to extend, automate, or integrate into custom workflows.

Simprint is being built to take a different direction: an open, programmable browser workspace for developers, researchers, operators, and automation-heavy teams. The goal is to make browser environments easier to control locally, easier to integrate with surrounding tools, and easier to evolve as workflows become more technical and more AI-assisted.

Features

• Isolated browser environments: Run multiple browser workspaces with separated state and operational boundaries.
• Persistent browser profiles: Keep long-lived browser profiles, account context, and workspace state organized over time.
• Proxy orchestration: Connect, assign, and manage proxy resources across environments and workflow scenarios.
• Fingerprint configuration: Control environment-level browser characteristics and continue refining fingerprint-related behavior.
• Local automation runtime: Build and run repeatable browser workflows for daily operations and task execution.
• Chromium-based desktop runtime: Run the workspace through a local Chromium-oriented Tauri + Rust desktop runtime with integrated frontend and system-level services.
• Syncer: Coordinate multiple running environments, choose a master session, and mirror interaction flows across selected windows.
• RPC bridge: Use the built-in Tauri command bridge between the React frontend and Rust services for desktop-native operations and orchestration.
• Local API: Expose workspace resources such as environments, proxies, tags, groups, and browser kernels through a local runtime API.
• MCP: Run a local Model Context Protocol service so external AI clients can connect to Simprint-managed tools and workspace resources.

Quick Start

Prerequisites

• Node.js 20
• pnpm 9
• Rust toolchain
• Tauri system prerequisites for your platform

Run locally

pnpm install --frozen-lockfile
cargo tauri dev

Starting the desktop application does not require any separately configured or running services.

Status

Simprint was originally developed as a hosted commercial product and has since moved to a local-first open-source desktop architecture. The open-source edition is intended to provide all core functionality without feature gating.

Some billing-related UI, upgrade prompts, or commercial entry points remain from the earlier architecture and will continue to be cleaned up over time.

Roadmap

• AI workflows: Expand AI-assisted operational flows and agent-oriented task orchestration.
• Local-first hardening: Improve local data migration, backup and restore, and offline behavior.
• Fingerprint research: Continue refining browser environment controls, compatibility, and research depth.
• Automation SDK: Provide a more reusable interface for building and integrating automation capabilities.

Data Use

Simprint stores its core business data on the user's device by default. Features that require network access, such as browser-kernel downloads, application updates, proxies, and external websites, still connect to the relevant third-party services.

Contributing

Simprint is in an active open-source transition, and we are looking for early contributors and future maintainers.

See CONTRIBUTING.md for development setup, contribution workflow, and pull request expectations.

Current high-value contribution areas include:

• Bug reports with reproducible steps and environment details
• Build, packaging, and CI improvements
• Documentation, onboarding, and local development experience
• Frontend UX polish and workflow consistency
• Tests, regression coverage, and release verification

Issues and pull requests are welcome. If you are interested in contributing on a longer horizon, please open an issue or discussion to introduce yourself and mention the areas you want to help maintain.

Friend Links

• LINUX DO - 新的理想型社区

License

This project is licensed under the GNU Affero General Public License v3.0 (AGPLv3).

If you want to use Simprint in a way that does not comply with the AGPLv3 obligations, including distributing modified versions or providing modified versions as a closed-source service, please contact us for a commercial license.