Jervis Man

Keep local Postman collections and environments in sync with a cloud workspace, with local storage and conflict review.

  • Project Type : Desktop · API workflows
  • Share :

Discuss your project

Share your requirements and the parts of your workflow you want to improve.

Jervis Man

Project Overview

Jervis Man keeps local Postman collections and environments connected to a team’s cloud workspace. Developers can pull remote changes, push local updates and keep a local copy of the data used in their API workflow.

The sync engine detects conflicting edits and applies defined policies. Content changed on both sides can require manual review, and the app exposes those conflicts to the user. Electron provides the desktop application, with SQLite for local storage.

The Challenge

  • Track local and remote changes across collections and environments.
  • Prevent the sync queue from processing the same operation repeatedly.
  • Make conflicting edits available for review before choosing a resolution.
  • Share the application logic between Windows and macOS builds.

How we built it

Vue 3 and Quasar provide the interface, with Pinia for state and Electron for the desktop shell. SQLite persists local data. A sync orchestrator, operation queue and conflict policies coordinate updates with the Postman API.

Technology Stack

  • Vue 3
  • Quasar
  • Electron
  • SQLite
  • Pinia
  • Vite
  • TypeScript

What the product Delivers

A desktop workspace for local Postman data and two-way cloud synchronization, with conflicts exposed for review when edits overlap.