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 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.

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
• Rust toolchain
• Tauri system prerequisites for your platform

One-line self-hosted server install

Linux servers can bootstrap the self-hosted backend with:

curl -fsSL https://raw.githubusercontent.com/Simprint/simprint/main/deploy/install-server.sh | bash # Update the client config afterwards, for example: base_url = http://127.0.0.1:40041/api/

Run locally

pnpm install
cp src-tauri/config.example.toml src-tauri/config.development.toml
cargo tauri dev --features development

Status

Simprint was originally developed as a commercial product. It is now being transitioned into an open-source project, and the current open-source edition is intended to provide all core functionality without feature gating.

Some billing-related UI, upgrade prompts, or commercial entry points may still appear in the product as remnants of the previous commercial model. These interfaces are being phased out and will be removed over time, while the related functionality will remain openly available in the community edition.

Roadmap

• AI workflows: Expand AI-assisted operational flows and agent-oriented task orchestration.
• Private deployment: Completed. Self-hosted and enterprise-controlled deployment support is now available.
• 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

Most users of the open-source edition will rely on community-hosted services, and related data may therefore be stored on community-managed servers. The community does not proactively disclose user data to third parties, but each user remains responsible for assessing their own data risk and should avoid submitting sensitive information whenever possible.

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.

Additional core components are also being prepared for broader collaboration over time, including the runtime process (simprint-runtime) and the browser-kernel layer (simprint-browser-kernel). The long-term goal is to build a maintainable open ecosystem around Simprint rather than keep contribution limited to the client surface.

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.