StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. DevOps
  3. Version Control
  4. Version Control System
  5. Mercurial vs Tiempo

Mercurial vs Tiempo

OverviewComparisonAlternatives

Overview

Mercurial
Mercurial
Stacks229
Followers219
Votes105
Tiempo
Tiempo
Stacks2
Followers7
Votes0

Mercurial vs Tiempo: What are the differences?

Introduction

In this markdown code, I will provide a comparison between Mercurial and Tiempo, outlining their key differences for a better understanding.

  1. Version Control System: Mercurial is a distributed version control system (DVCS) that allows multiple developers to work on the same project simultaneously, tracking changes made to files and efficiently managing versions. On the other hand, Tiempo is not a version control system but a provider of software development services focused on delivering high-quality software solutions.

  2. Purpose: Mercurial is designed specifically for source code management and is commonly used by software development teams to manage their codebase, track changes, and collaborate effectively. In contrast, Tiempo focuses on providing software development, testing, and support services to enhance the productivity of businesses and generate software solutions tailored to their specific needs.

  3. Workflow: Mercurial employs a decentralized workflow, where each developer has their own copy of the repository and can work on it independently. Changes can be easily pushed and pulled between repositories, enabling efficient collaboration. In contrast, Tiempo follows a client-service provider workflow, where clients request software development services from Tiempo's expert teams, who then work on the projects using their own tools and methodologies.

  4. Feature Set: Mercurial offers a wide range of features and capabilities to support source code management, including branch management, version history tracking, merging, and conflict resolution. It provides robust support for large-scale projects and offers various extensions to enhance functionality. Conversely, Tiempo does not provide a specific feature set like Mercurial, as it offers comprehensive software development services encompassing various technologies, platforms, and programming languages.

  5. Community Support: Mercurial has an active and engaged community of users and developers who contribute to its development, provide support, and continuously enhance its features. This community support ensures that any issues and bugs are addressed promptly. Tiempo, being a software development service provider, relies on its own team of experts to provide support and ensure the delivery of high-quality software solutions.

  6. Cost: Mercurial is an open-source tool, meaning it is free for anyone to use, modify, and distribute. It can be downloaded and installed without any licensing costs. On the other hand, Tiempo is a service-based company that charges for its software development services based on the scope, complexity, and duration of projects.

In summary, Mercurial is a distributed version control system specifically designed for source code management, while Tiempo is a software development service provider. Mercurial focuses on supporting collaborative software development workflows with its comprehensive feature set, active community support, and zero cost, whereas Tiempo offers a wide range of software development services tailored to clients' needs and charges for these services.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Detailed Comparison

Mercurial
Mercurial
Tiempo
Tiempo

Mercurial is dedicated to speed and efficiency with a sane user interface. It is written in Python. Mercurial's implementation and data structures are designed to be fast. You can generate diffs between revisions, or jump back in time within seconds.

Tiempo is custom tracking, approval, and payments for your contract workers. Whether you pay by the hour, project, word, or widget, Tiempo's got you covered. Quickly look across your workforce to understand who's been working, what they’ve done, and what they’re owed.

-
Whether you pay by the hour, project, word, or widget, Tiempo's got you covered. Available on the Web, iOS, and Android.;Quickly look across your workforce to understand who's been working, what they’ve done, and what they’re owed;Tiempo collects your contractors’ bank information. No more awkward conversations. Just sit back and tap to pay when you're ready.
Statistics
Stacks
229
Stacks
2
Followers
219
Followers
7
Votes
105
Votes
0
Pros & Cons
Pros
  • 18
    A lot easier to extend than git
  • 17
    Easy-to-grasp system with nice tools
  • 13
    Works on windows natively without cygwin nonsense
  • 11
    Written in python
  • 9
    Free
Cons
  • 0
    Does not distinguish between local and remote head
  • 0
    Track single upstream only
No community feedback yet
Integrations
Windows
Windows
Fedora
Fedora
FreeBSD
FreeBSD
Debian
Debian
Gentoo Linux
Gentoo Linux
Mac OS X
Mac OS X
No integrations available

What are some alternatives to Mercurial, Tiempo?

Git

Git

Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency.

SVN (Subversion)

SVN (Subversion)

Subversion exists to be universally recognized and adopted as an open-source, centralized version control system characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations.

Toggl

Toggl

Toggl is an online time-tracking tool. It is popular with freelancers, groups, and small companies all over the world, mostly in US, Canada and UK.

Plastic SCM

Plastic SCM

Plastic SCM is a distributed version control designed for big projects. It excels on branching and merging, graphical user interfaces, and can also deal with large files and even file-locking (great for game devs). It includes "semantic" features like refactor detection to ease diffing complex refactors.

Pijul

Pijul

Pijul is a free and open source (AGPL 3) distributed version control system. Its distinctive feature is to be based on a sound theory of patches, which makes it easy to learn and use, and really distributed.

Everhour

Everhour

Everhour put all the control of your timesheets, budgeting, employee scheduling,
expenses and invoicing in an elegant, beautiful and really useful way.

Simple

Simple

Time is the most precious resource we have, despite that, most people don't know where all their time goes. With Simple, you’ll see exactly where your time was spent.

DVC

DVC

It is an open-source Version Control System for data science and machine learning projects. It is designed to handle large files, data sets, machine learning models, and metrics as well as code.

Magit

Magit

It is an interface to the version control system Git, implemented as an Emacs package. It aspires to be a complete Git porcelain. While we cannot (yet) claim that it wraps and improves upon each and every Git command, it is complete enough to allow even experienced Git users to perform almost all of their daily version control tasks directly from within Emacs. While many fine Git clients exist, only deserve to be called porcelains.

Punchtime for Trello

Punchtime for Trello

Manage your projects with Trello, track time with Punchtime. Log work: describe what you did, for how long, and who participated. Categorize your work with Trello cards or labels. Drill down with powerful filters and give your estimates a reality check.

Related Comparisons

GitHub
Bitbucket

Bitbucket vs GitHub vs GitLab

GitHub
Bitbucket

AWS CodeCommit vs Bitbucket vs GitHub

Kubernetes
Rancher

Docker Swarm vs Kubernetes vs Rancher

gulp
Grunt

Grunt vs Webpack vs gulp

Graphite
Kibana

Grafana vs Graphite vs Kibana