Alternatives to gopass logo

Alternatives to gopass

KeePass, Vault, Slack, Jira, and Trello are the most popular alternatives and competitors to gopass.
13
24
+ 1
5

What is gopass and what are its top alternatives?

Gopass is a password manager that allows users to store and manage their passwords securely. Key features include encryption, password generation, and cross-platform compatibility. However, some limitations of gopass include a lack of advanced features compared to other password managers and a steeper learning curve for new users.

  1. LastPass: LastPass offers features like password autofill, password generator, secure notes, and multi-factor authentication. Pros include user-friendly interface and browser extensions, while cons include limited free version features and occasional security concerns.
  2. Bitwarden: Bitwarden is an open-source password manager that supports various platforms and offers features like password sharing and secure notes. Pros include strong encryption and affordable premium plans, while cons include occasional syncing issues.
  3. 1Password: 1Password provides features like secure password storage, password generator, and travel mode for secure access on the go. Pros include user-friendly interface and strong security measures, while cons include higher pricing compared to other alternatives.
  4. Dashlane: Dashlane offers features like password changer, digital wallet, and secure sharing. Pros include user-friendly interface and password breach alerts, while cons include limited free version features and higher pricing.
  5. KeePass: KeePass is an open-source password manager that allows users to store passwords locally or in a cloud service of their choice. Pros include high level of customization and strong security measures, while cons include lack of official mobile apps.
  6. RoboForm: RoboForm offers features like password manager, form filling, and secure sharing. Pros include user-friendly interface and secure password storage, while cons include limitations in the free version and occasional syncing issues.
  7. NordPass: NordPass provides features like secure password storage, password generator, and biometric authentication. Pros include strong encryption and affordable pricing, while cons include limited features in the free version.
  8. Enpass: Enpass offers features like password manager, password generator, and secure notes. Pros include local storage of passwords and affordable pricing, while cons include lack of some advanced features compared to competitors.
  9. Keeper: Keeper provides features like secure password storage, password generator, and dark web monitoring. Pros include strong encryption and user-friendly interface, while cons include higher pricing for family plans.
  10. RememBear: RememBear offers features like password manager, auto-fill, and secure notes. Pros include user-friendly interface and affordable pricing, while cons include limited features compared to other alternatives.

Top Alternatives to gopass

  • KeePass
    KeePass

    It is an open source password manager. Passwords can be stored in highly-encrypted databases, which can be unlocked with one master password or key file. ...

  • Vault
    Vault

    Vault is a tool for securely accessing secrets. A secret is anything that you want to tightly control access to, such as API keys, passwords, certificates, and more. Vault provides a unified interface to any secret, while providing tight access control and recording a detailed audit log. ...

  • Slack
    Slack

    Imagine all your team communication in one place, instantly searchable, available wherever you go. That’s Slack. All your messages. All your files. And everything from Twitter, Dropbox, Google Docs, Asana, Trello, GitHub and dozens of other services. All together. ...

  • Jira
    Jira

    Jira's secret sauce is the way it simplifies the complexities of software development into manageable units of work. Jira comes out-of-the-box with everything agile teams need to ship value to customers faster. ...

  • Trello
    Trello

    Trello is a collaboration tool that organizes your projects into boards. In one glance, Trello tells you what's being worked on, who's working on what, and where something is in a process. ...

  • G Suite
    G Suite

    An integrated suite of secure, cloud-native collaboration and productivity apps. It includes Gmail, Docs, Drive, Calendar, Meet and more. ...

  • Confluence
    Confluence

    Capture the knowledge that's too often lost in email inboxes and shared network drives in Confluence instead – where it's easy to find, use, and update. ...

  • Skype
    Skype

    Skype’s text, voice and video make it simple to share experiences with the people that matter to you, wherever they are. ...

gopass alternatives & related posts

KeePass logo

KeePass

69
30
A free and open source password manager
69
30
PROS OF KEEPASS
  • 9
    Free
  • 7
    Password stored encrypted
  • 4
    Password Generator
  • 3
    Plugings
  • 3
    Advanced Search
  • 3
    Import & Export
  • 1
    Biometric unlock
  • 0
    TOTP
CONS OF KEEPASS
  • 1
    Password share is unencrypted
  • 0
    Free

related KeePass posts

Vault logo

Vault

798
71
Secure, store, and tightly control access to tokens, passwords, certificates, API keys, and other secrets in modern computing
798
71
PROS OF VAULT
  • 17
    Secure
  • 13
    Variety of Secret Backends
  • 11
    Very easy to set up and use
  • 8
    Dynamic secret generation
  • 5
    AuditLog
  • 3
    Privilege Access Management
  • 3
    Leasing and Renewal
  • 2
    Easy to integrate with
  • 2
    Open Source
  • 2
    Consol integration
  • 2
    Handles secret sprawl
  • 2
    Variety of Auth Backends
  • 1
    Multicloud
CONS OF VAULT
    Be the first to leave a con

    related Vault posts

    Tymoteusz Paul
    Devops guy at X20X Development LTD · | 23 upvotes · 10.1M views

    Often enough I have to explain my way of going about setting up a CI/CD pipeline with multiple deployment platforms. Since I am a bit tired of yapping the same every single time, I've decided to write it up and share with the world this way, and send people to read it instead ;). I will explain it on "live-example" of how the Rome got built, basing that current methodology exists only of readme.md and wishes of good luck (as it usually is ;)).

    It always starts with an app, whatever it may be and reading the readmes available while Vagrant and VirtualBox is installing and updating. Following that is the first hurdle to go over - convert all the instruction/scripts into Ansible playbook(s), and only stopping when doing a clear vagrant up or vagrant reload we will have a fully working environment. As our Vagrant environment is now functional, it's time to break it! This is the moment to look for how things can be done better (too rigid/too lose versioning? Sloppy environment setup?) and replace them with the right way to do stuff, one that won't bite us in the backside. This is the point, and the best opportunity, to upcycle the existing way of doing dev environment to produce a proper, production-grade product.

    I should probably digress here for a moment and explain why. I firmly believe that the way you deploy production is the same way you should deploy develop, shy of few debugging-friendly setting. This way you avoid the discrepancy between how production work vs how development works, which almost always causes major pains in the back of the neck, and with use of proper tools should mean no more work for the developers. That's why we start with Vagrant as developer boxes should be as easy as vagrant up, but the meat of our product lies in Ansible which will do meat of the work and can be applied to almost anything: AWS, bare metal, docker, LXC, in open net, behind vpn - you name it.

    We must also give proper consideration to monitoring and logging hoovering at this point. My generic answer here is to grab Elasticsearch, Kibana, and Logstash. While for different use cases there may be better solutions, this one is well battle-tested, performs reasonably and is very easy to scale both vertically (within some limits) and horizontally. Logstash rules are easy to write and are well supported in maintenance through Ansible, which as I've mentioned earlier, are at the very core of things, and creating triggers/reports and alerts based on Elastic and Kibana is generally a breeze, including some quite complex aggregations.

    If we are happy with the state of the Ansible it's time to move on and put all those roles and playbooks to work. Namely, we need something to manage our CI/CD pipelines. For me, the choice is obvious: TeamCity. It's modern, robust and unlike most of the light-weight alternatives, it's transparent. What I mean by that is that it doesn't tell you how to do things, doesn't limit your ways to deploy, or test, or package for that matter. Instead, it provides a developer-friendly and rich playground for your pipelines. You can do most the same with Jenkins, but it has a quite dated look and feel to it, while also missing some key functionality that must be brought in via plugins (like quality REST API which comes built-in with TeamCity). It also comes with all the common-handy plugins like Slack or Apache Maven integration.

    The exact flow between CI and CD varies too greatly from one application to another to describe, so I will outline a few rules that guide me in it: 1. Make build steps as small as possible. This way when something breaks, we know exactly where, without needing to dig and root around. 2. All security credentials besides development environment must be sources from individual Vault instances. Keys to those containers should exist only on the CI/CD box and accessible by a few people (the less the better). This is pretty self-explanatory, as anything besides dev may contain sensitive data and, at times, be public-facing. Because of that appropriate security must be present. TeamCity shines in this department with excellent secrets-management. 3. Every part of the build chain shall consume and produce artifacts. If it creates nothing, it likely shouldn't be its own build. This way if any issue shows up with any environment or version, all developer has to do it is grab appropriate artifacts to reproduce the issue locally. 4. Deployment builds should be directly tied to specific Git branches/tags. This enables much easier tracking of what caused an issue, including automated identifying and tagging the author (nothing like automated regression testing!).

    Speaking of deployments, I generally try to keep it simple but also with a close eye on the wallet. Because of that, I am more than happy with AWS or another cloud provider, but also constantly peeking at the loads and do we get the value of what we are paying for. Often enough the pattern of use is not constantly erratic, but rather has a firm baseline which could be migrated away from the cloud and into bare metal boxes. That is another part where this approach strongly triumphs over the common Docker and CircleCI setup, where you are very much tied in to use cloud providers and getting out is expensive. Here to embrace bare-metal hosting all you need is a help of some container-based self-hosting software, my personal preference is with Proxmox and LXC. Following that all you must write are ansible scripts to manage hardware of Proxmox, similar way as you do for Amazon EC2 (ansible supports both greatly) and you are good to go. One does not exclude another, quite the opposite, as they can live in great synergy and cut your costs dramatically (the heavier your base load, the bigger the savings) while providing production-grade resiliency.

    See more
    Joseph Irving
    DevOps Engineer at uSwitch · | 8 upvotes · 23.7K views

    At uSwitch we use Vault to generate short lived database credentials for our applications running in Kubernetes. We wanted to move from an environment where we had 100 dbs with a variety of static passwords being shared around to a place where each pod would have credentials that only last for its lifetime.

    We chose vault because:

    • It had built in Kubernetes support so we could use service accounts to permission which pods could access which database.

    • A terraform provider so that we could configure both our RDS instances and their vault configuration in one place.

    • A variety of database providers including MySQL/PostgreSQL (our most common dbs).

    • A good api/Go -sdk so that we could build tooling around it to simplify development worfklow.

    • It had other features we would utilise such as PKI

    See more
    Slack logo

    Slack

    120.1K
    6K
    Bring all your communication together in one place
    120.1K
    6K
    PROS OF SLACK
    • 1.2K
      Easy to integrate with
    • 876
      Excellent interface on multiple platforms
    • 849
      Free
    • 694
      Mobile friendly
    • 690
      People really enjoy using it
    • 331
      Great integrations
    • 315
      Flexible notification preferences
    • 198
      Unlimited users
    • 184
      Strong search and data archiving
    • 155
      Multi domain switching support
    • 82
      Easy to use
    • 40
      Beautiful
    • 27
      Hubot support
    • 22
      Unread/read control
    • 21
      Slackbot
    • 19
      Permalink for each messages
    • 17
      Text snippet with highlighting
    • 15
      Quote message easily
    • 14
      Per-room notification
    • 13
      Awesome integration support
    • 12
      Star for each message / attached files
    • 12
      IRC gateway
    • 11
      Good communication within a team
    • 11
      Dropbox Integration
    • 10
      Slick, search is great
    • 10
      Jira Integration
    • 9
      New Relic Integration
    • 8
      Great communication tool
    • 8
      Combine All Services Quickly
    • 8
      Asana Integration
    • 7
      This tool understands developers
    • 7
      XMPP gateway
    • 7
      Google Drive Integration
    • 7
      Awesomeness
    • 6
      Replaces email
    • 6
      Twitter Integration
    • 6
      Google Docs Integration
    • 6
      BitBucket integration
    • 5
      Jenkins Integration
    • 5
      GREAT Customer Support / Quick Response to Feedback
    • 5
      Guest and Restricted user control
    • 4
      Clean UI
    • 4
      Excellent multi platform internal communication tool
    • 4
      GitHub integration
    • 4
      Mention list view
    • 4
      Gathers all my communications in one place
    • 3
      Perfect implementation of chat + integrations
    • 3
      Easy
    • 3
      Easy to add a reaction
    • 3
      Timely while non intrusive
    • 3
      Great on-boarding
    • 3
      Threaded chat
    • 3
      Visual Studio Integration
    • 3
      Easy to start working with
    • 3
      Android app
    • 2
      Simplicity
    • 2
      Message Actions
    • 2
      It's basically an improved (although closed) IRC
    • 2
      So much better than email
    • 2
      Eases collaboration for geographically dispersed teams
    • 2
      Great interface
    • 2
      Great Channel Customization
    • 2
      Markdown
    • 2
      Intuitive, easy to use, great integrations
    • 1
      Great Support Team
    • 1
      Watch
    • 1
      Multi work-space support
    • 1
      Flexible and Accessible
    • 1
      Better User Experience
    • 1
      Archive Importing
    • 1
      Travis CI integration
    • 1
      It's the coolest IM ever
    • 1
      Community
    • 1
      Great API
    • 1
      Easy remote communication
    • 1
      Get less busy
    • 1
      API
    • 1
      Zapier integration
    • 1
      Targetprocess integration
    • 1
      Finally with terrible "threading"—I miss Flowdock
    • 1
      Complete with plenty of Electron BLOAT
    • 1
      I was 666 star :D
    • 1
      Dev communication Made Easy
    • 1
      Integrates with just about everything
    • 1
      Very customizable
    • 0
      Platforms
    • 0
      Easy to useL
    CONS OF SLACK
    • 13
      Can be distracting depending on how you use it
    • 6
      Requires some management for large teams
    • 6
      Limit messages history
    • 5
      Too expensive
    • 5
      You don't really own your messages
    • 4
      Too many notifications by default

    related Slack posts

    Lucas Litton
    Founder & CEO at Macombey · | 24 upvotes · 340.9K views

    Sentry has been essential to our development approach. Nobody likes errors or apps that crash. We use Sentry heavily during Node.js and React development. Our developers are able to see error reports, crashes, user's browsers, and more, all in one place. Sentry also seamlessly integrates with Asana, Slack, and GitHub.

    See more
    Jakub Olan
    Node.js Software Engineer · | 17 upvotes · 470K views

    Last time we shared there information about our decision about using YouTrack over Jira actually we found much better solution that our team have loved. Linear is a minimalistic issue tracker that integrates well with Sentry, GitHub, Slack and Figma which are our basic tools. I would like to recommend checking out Linear as a potential alternative to "heavy" issue trackers, maybe at enterprises that may not work but when we're a startup that works awesome!

    See more
    Jira logo

    Jira

    61.8K
    1.2K
    The #1 software development tool used by agile teams to plan, track, and release great software.
    61.8K
    1.2K
    PROS OF JIRA
    • 310
      Powerful
    • 254
      Flexible
    • 149
      Easy separation of projects
    • 113
      Run in the cloud
    • 105
      Code integration
    • 58
      Easy to use
    • 53
      Run on your own
    • 39
      Great customization
    • 39
      Easy Workflow Configuration
    • 27
      REST API
    • 12
      Great Agile Management tool
    • 7
      Integrates with virtually everything
    • 6
      Confluence
    • 6
      Complicated
    • 3
      Sentry Issues Integration
    • 2
      It's awesome
    CONS OF JIRA
    • 8
      Rather expensive
    • 5
      Large memory requirement
    • 2
      Slow
    • 1
      Cloud or Datacenter only

    related Jira posts

    Johnny Bell

    So I am a huge fan of JIRA like #massive I used it for many many years, and really loved it, used it personally and at work. I would suggest every new workplace that I worked at to switch to JIRA instead of what I was using.

    When I started at #StackShare we were using a Trello #Kanban board and I was so shocked at how easy the workflow was to follow, create new tasks and get tasks QA'd and deployed. What was so great about this was it didn't come with all the complexity of JIRA. Like setting up a project, user rules etc. You are able to hit the ground running with Trello and get tasks started right away without being overwhelmed with the complexity of options in JIRA

    With a few TrelloPowerUps we were easily able to add GitHub integration and storyPoints to our cards and thats all we needed to get a really nice agile workflow going.

    I'm not saying that JIRA is not useful, I can see larger companies being able to use the JIRA features and have the time to go through all the complex setup to get a really good workflow going. But for smaller #Startups that want to hit the ground running Trello for me is the way to go.

    In saying that what I would love Trello to implement is to allow me to create custom fields. Right now we just have a Description field. So I am adding User Stories & How To Test in the Markdown of the Description if I could have these as custom fields then my #Agile workflow would be complete.

    #StackDecisionsLaunch

    See more
    Jakub Olan
    Node.js Software Engineer · | 17 upvotes · 470K views

    Last time we shared there information about our decision about using YouTrack over Jira actually we found much better solution that our team have loved. Linear is a minimalistic issue tracker that integrates well with Sentry, GitHub, Slack and Figma which are our basic tools. I would like to recommend checking out Linear as a potential alternative to "heavy" issue trackers, maybe at enterprises that may not work but when we're a startup that works awesome!

    See more
    Trello logo

    Trello

    43.3K
    3.7K
    Your entire project, in a single glance
    43.3K
    3.7K
    PROS OF TRELLO
    • 715
      Great for collaboration
    • 628
      Easy to use
    • 573
      Free
    • 375
      Fast
    • 347
      Realtime
    • 237
      Intuitive
    • 215
      Visualizing
    • 169
      Flexible
    • 126
      Fun user interface
    • 83
      Snappy and blazing fast
    • 30
      Simple, intuitive UI that gets out of your way
    • 27
      Kanban
    • 21
      Clean Interface
    • 18
      Easy setup
    • 18
      Card Structure
    • 17
      Drag and drop attachments
    • 11
      Simple
    • 10
      Markdown commentary on cards
    • 9
      Lists
    • 9
      Integration with other work collaborative apps
    • 8
      Satisfying User Experience
    • 8
      Cross-Platform Integration
    • 7
      Recognizes GitHub commit links
    • 6
      Easy to learn
    • 5
      Great
    • 4
      Better than email
    • 4
      Versatile Team & Project Management
    • 3
      and lots of integrations
    • 3
      Trello’s Developmental Transparency
    • 3
      Effective
    • 2
      Easy
    • 2
      Powerful
    • 2
      Agile
    • 2
      Easy to have an overview of the project status
    • 2
      flexible and fast
    • 2
      Simple and intuitive
    • 1
      Name rolls of the tongue
    • 1
      Customizable
    • 1
      Email integration
    • 1
      Personal organisation
    • 1
      Nice
    • 1
      Great organizing (of events/tasks)
    • 0
      Easiest way to visually express the scope of projects
    CONS OF TRELLO
    • 5
      No concept of velocity or points
    • 4
      Very light native integrations
    • 2
      A little too flexible

    related Trello posts

    Johnny Bell

    So I am a huge fan of JIRA like #massive I used it for many many years, and really loved it, used it personally and at work. I would suggest every new workplace that I worked at to switch to JIRA instead of what I was using.

    When I started at #StackShare we were using a Trello #Kanban board and I was so shocked at how easy the workflow was to follow, create new tasks and get tasks QA'd and deployed. What was so great about this was it didn't come with all the complexity of JIRA. Like setting up a project, user rules etc. You are able to hit the ground running with Trello and get tasks started right away without being overwhelmed with the complexity of options in JIRA

    With a few TrelloPowerUps we were easily able to add GitHub integration and storyPoints to our cards and thats all we needed to get a really nice agile workflow going.

    I'm not saying that JIRA is not useful, I can see larger companies being able to use the JIRA features and have the time to go through all the complex setup to get a really good workflow going. But for smaller #Startups that want to hit the ground running Trello for me is the way to go.

    In saying that what I would love Trello to implement is to allow me to create custom fields. Right now we just have a Description field. So I am adding User Stories & How To Test in the Markdown of the Description if I could have these as custom fields then my #Agile workflow would be complete.

    #StackDecisionsLaunch

    See more
    Francisco Quintero
    Tech Lead at Dev As Pros · | 13 upvotes · 1.8M views

    For Etom, a side project. We wanted to test an idea for a future and bigger project.

    What Etom does is searching places. Right now, it leverages the Google Maps API. For that, we found a React component that makes this integration easy because using Google Maps API is not possible via normal API requests.

    You kind of need a map to work as a proxy between the software and Google Maps API.

    We hate configuration(coming from Rails world) so also decided to use Create React App because setting up a React app, with all the toys, it's a hard job.

    Thanks to all the people behind Create React App it's easier to start any React application.

    We also chose a module called Reactstrap which is Bootstrap UI in React components.

    An important thing in this side project(and in the bigger project plan) is to measure visitor through out the app. For that we researched and found that Keen was a good choice(very good free tier limits) and also it is very simple to setup and real simple to send data to

    Slack and Trello are our defaults tools to comunicate ideas and discuss topics, so, no brainer using them as well for this project.

    See more
    G Suite logo

    G Suite

    31.6K
    2.5K
    Collaboration and productivity apps for Business
    31.6K
    2.5K
    PROS OF G SUITE
    • 609
      Gmail
    • 447
      Google docs
    • 365
      Calendar
    • 284
      Great for startups
    • 230
      Easy to work
    • 115
      Document management & workflow
    • 110
      Very easy to share
    • 80
      No brainer
    • 59
      Google groups
    • 59
      Google scripts & api
    • 22
      Google drive
    • 16
      Popular
    • 13
      No spam, phishing protection
    • 12
      Google Spreadsheets
    • 12
      Easy
    • 10
      Cloud based and collaboration
    • 7
      Simple and fast document creation collaboration
    • 6
      Best Cloud environment ever
    • 5
      Google maps api
    • 3
      Awesome Collaboration Tools
    • 3
      Google-powered Search in Gmail
    • 3
      Geolocation
    • 1
      도메인 단위로 어플을 관리할 수 있고, 클라우드지만 강력한 보안기능과 기기관리 기능을 제공
    • 1
      music
    • 1
      Single sign-on
    • 1
      Simple
    CONS OF G SUITE
    • 6
      Starting to get pricey
    • 4
      Good luck changing domains
    • 1
      Lesser fonts and styling available in mail compose
    • 1
      Long emails get truncated

    related G Suite posts

    Yonas Beshawred

    Using Screenhero via Slack was getting to be pretty horrible. Video and sound quality was often times pretty bad and worst of all the service just wasn't reliable. We all had high hopes when the acquisition went through but ultimately, the product just didn't live up to expectations. We ended up trying Zoom after I had heard about it from some friends at other companies. We noticed the video/sound quality was better, and more importantly it was super reliable. The Slack integration was awesome (just type /zoom and it starts a call)

    You can schedule recurring calls which is helpful. There's a G Suite (Google Calendar) integration which lets you add a Zoom call (w/dial in info + link to web/mobile) with the click of a button.

    Meeting recordings (video and audio) are really nice, you get recordings stored in the cloud on the higher tier plans. One of our engineers, Jerome, actually built a cool little Slack integration using the Slack API and Zoom API so that every time a recording is processed, a link gets posted to the "event-recordings" channel. The iOS app is great too!

    #WebAndVideoConferencing #videochat

    See more
    Nasser Khan
    Product Manager at StackShare · | 13 upvotes · 446.6K views
    Shared insights
    on
    G SuiteG SuiteSlackSlack
    at

    We are highly dependent on G Suite for all our collaboration and productivity needs, from Gmail and Calendar to Sheets and Docs. While it may not be as robust as Microsoft's offerings in those areas, it's totally cloud-based, we've never had any downtime issues and it integrates well with our other tools like Slack. We write and collaborate on all our specs/PRDs in Docs, share analyses via Sheets and handle our meetings via Calendar. #StackDecisionsLaunch #ProductivitySuite #Collaboration #DocumentCollaboration

    See more
    Confluence logo

    Confluence

    26.5K
    202
    One place to share, find, and collaborate on information
    26.5K
    202
    PROS OF CONFLUENCE
    • 94
      Wiki search power
    • 62
      WYSIWYG editor
    • 43
      Full featured, works well with embedded docs
    • 3
      Expensive licenses
    CONS OF CONFLUENCE
    • 3
      Expensive license

    related Confluence posts

    David Ritsema
    Frontend Architect at Herman Miller · | 11 upvotes · 721.8K views

    We knew how we wanted to build our Design System, now it was time to choose the tools to get us there. The essence of Scrum is a small team of people. The team is highly flexible and adaptive. Perfect, so we'll work in 2 week sprints where each sprint can be a mix of new R&D stories, a presentation of decisions made, and showcasing key development milestones.

    We are also able to run content stories in parallel, focusing development efforts around key areas of the site that our authors need first. Our stories would exist in a Jira backlog, documentation would be hosted in Confluence , and GitHub would host our codebase. If developers identify technical improvements during the sprint, they can be added as GitHub issues and transferred to Jira if we decide to represent them as stories for the Backlog. For Sprint Retrospectives, @groupmap proved to be a great way to include our remote members of the dev team.

    This worked well for our team and allowed us to be flexible in what we wanted to build and how we wanted to build it. As we further defined our Backlog and estimated each story, we could accurately measure the team's capacity (velocity) and confidently estimate a launch date.

    See more
    Priit Kaasik
    CTO at Katana Cloud Inventory · | 9 upvotes · 572.7K views

    As a new company we could early adopt and bet on #RemoteTeam setup without cultural baggage derailing us. Our building blocks for developing remote working culture are:

    • Hiring people who are self sufficient, self-disciplined and excel at video and written communication to work remotely
    • Set up periodic ceremonies ( #DailyStandup, #Grooming, Release calls and chats etc) to keep the company rhythm / heartbeat going across remote cells
    • Regularly train your leaders to take into account remote working aspects of organizing f2f calls, events, meetups, parties etc. when communicating and organizing workflows
    • And last, but not least - select the right tools to support effective communication and collaboration:
    1. All feeds and conversations come together in Slack
    2. #Agile workflows in Jira
    3. InProductCommunication and #CustomerSupportChat in Intercom
    4. #Notes, #Documentation and #Requirements in Confluence
    5. #SourceCode and ContinuousDelivery in Bitbucket
    6. Persistent video streams between locations, demos, meetings run on appear.in
    7. #Logging and Alerts in Papertrail
    See more
    Skype logo

    Skype

    17.2K
    653
    Voice calls, instant messaging, file transfer, and video conferencing
    17.2K
    653
    PROS OF SKYPE
    • 258
      Free, widespread
    • 147
      Desktop and mobile apps
    • 110
      Because i have to :(
    • 57
      Low cost international calling
    • 56
      Good for international calls
    • 10
      Best call quality anywhere, generally
    • 5
      Beautiful emojis
    • 4
      Chat bots
    • 2
      Translator
    • 2
      Skype for business integration with Outlook
    • 1
      United kingdom
    • 1
      Not the Best, but get the job done
    CONS OF SKYPE
    • 5
      Really high CPU utilization during video/screenshare
    • 3
      Not always reliable
    • 3
      Outdated UI
    • 3
      Birthday notifications are annoying
    • 3
      The worst indicator noises of any app ever
    • 2
      Finding/adding people isn't easy

    related Skype posts

    Dmitry Mukhin

    Uploadcare is mostly remote team and we're using video conferencing all the time both for internal team meetings and for external sales, support, interview, etc. calls. I think we've tried every solution there is on the market before we've decided to stop with Zoom.

    Tools just plainly don't work (Skype), are painful to install for external participants (Webex and other "enterprise" solutions) can't properly handle 10+ participants calls (Google Hangouts Chat).

    Zoom just works. It has all required features and even handles bad connections very graciously. One of the best tool decisions we've ever made :)

    See more
    Mark Nelissen

    I use Slack because it offers the best experience, even on the free tier (which we're still using). As a comparison, I have had in depth experience with HipChat, Stride, Skype, Google Chat (the new service), Google Hangouts (the old service). For self hosted, Mattermost is open source and claims to support most Slack integrations, but I have not extensively investigated this claim.

    See more