Australian company Atlassian offers Bamboo, a continuous integration server.
$1,200
1 remote agent
Confluence
Score 8.1 out of 10
N/A
Confluence is a collaboration and content sharing platform used primarily by customers who are already using Atlassian's Jira project tracking product. The product appeals particularly to IT users.
$6.40
per month per user
Pricing
Atlassian Bamboo
Atlassian Confluence
Editions & Modules
1 Remote Agent
$1200
5 Remote Agents
$3200
10 Remote Agents
$5840
25 Remote Agents
$11,600
100 Remote Agents
$23,280
250 Remote Agents
$58,160
500 Remote Agents
$87,280
1000 Remote Agents
$133,840
2000 Remote Agents
$187,380
Free
$0
Free for 10 Users
Standard
$6.40
per month per user
Premium
$12.30
per month per user
Data Center
220,000.00
40,001+ Users - Annually
Enterprise
Contact Sales
Offerings
Pricing Offerings
Atlassian Bamboo
Confluence
Free Trial
No
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
Prices shown here reflect prices for deployments with 100 users or less. The prices decrease wien the user base surpasses 100.
More Pricing Information
Community Pulse
Atlassian Bamboo
Atlassian Confluence
Considered Both Products
Atlassian Bamboo
Verified User
Engineer
Chose Atlassian Bamboo
Bamboo is hands-down the best of these options if you rely on other products of Atlassian origin. Bamboo is not just built for teams, but teams-of-teams and teams of many workers. It has the administrative features you need to manage and maintain CI at scale. Enterprise model …
Bamboo won solely based on the fact we were "all-in" with Atlassian. TeamCity is now in the process of taking over as we transition off of Bamboo, and I think TeamCity stacks up nice against Bamboo thus far (too soon to tell).
We selected Bamboo because its capabilities to integrate with other Atlassian products specially Jira Software, Bitbucket and in some useful scenarios with Confluence. Also, we found these pros important for us: great user interface, easily agent deployment, Docker …
Bamboo is great tool when compared to the open-source alternative Jenkins, with mainly the same functionality in both it really shines with its integration of the Atlassian product line. Jenkins works really well with a huge community of users and plenty of plugins that are …
We chose Bamboo over Jenkins for 2 reasons - one, for its tight integration amongst all the products in the tool suite. We find explicit value in the traceability from JIRA issues all the way down to the Bamboo build that was triggered by the check in of those issues. The …
Jenkins works great, but Bamboo is just fantastic when integrated with other Atlassian tools. Since we were using JIRA and Bitbucket, we went for Bamboo.
I use bamboo because it is mandated as the CI/CD solution to use across the organization that I work for. If I were working on my own project, I would almost certainly use a free solution like Travis CI or just spin up my own build servers using Docker, AWS, or something like …
Bamboo integrates directly with our bug system (JIRA) and source control system (Bitbucket). It allows us to get what we need to done without worrying about how it works with our other systems.
As we are using an Atlassian package, it fits in our stack, which helps us make our development faster and more trackable. There are lots of reason to select Atlassian Confluence is that it fits well in our stack and it is very useful and handy tool to use. I am not sure how it …
For our needs, Confluence absolutely blew both SharePoint and Google Docs out of the water. We were able to get more granular security than with SharePoint while maintaining the collaborative tool sets found in both SharePoint and Google Docs. Additionally, the integration into …
If you value integration over cost, Bamboo is clearly the way to go. It offers tight integration to the rest of the Atlassian suite, and when you need traceability from issue to build, Atlassian is the right way to go. However, if you find yourself needing to save on costs, you may consider taking an approach of rolling your own build system with open source alternatives, such as Jenkins, if you don't [mind] putting in a little extra elbow grease.
I would recommend Atlassian Confluence for companies that want to have internal documentation and minimum governance processes to ensure documentation is useful and doesn't have a lot of duplicated and non-updated content. I wouldn't recommend Atlassian Confluence for companies with a low budget since this product might be a little costly (especially with add-ons).
Levels of granularity. Organization has many projects that have many build plans that have many jobs that have many tasks, etc. And branch builds allow source control branches to be built separately.
Versatility. I can use bamboo to manage my Java, node, or .NET build plans. I can use it to spin up Windows or Linux build agents, or install it on a Mac to build there as well.
Bamboo integrates with other Atlassian products like Bitbucket, Stash, JIRA, etc. If a company commits to the entire Atlassian stack then work can be tracked through the whole development lifecycle which is really useful.
Cross product linking - If you use other Atlassian products then Atlassian Confluence is a no-brainer for your source of documentation, knowledge management etc. You can show previews of the linked asset natively E.g. showing a preview of a JIRA ticket in a Atlassian Confluence page.
Simple editing - Though the features available may not be super complex right now, this does come with the benefit of making it easy to edit and create documents. Some documentation editors can be overwhelming, Atlassian Confluence is simple and intuitive.
Native marketplace - If you want to install add-ons to your Atlassian Confluence space it's really easy. Admins can explore the Atlassian marketplace natively and install them to your instance in a few clicks. You can customise your Atlassian Confluence instance in many different ways using add-ons.
UI Design is very simplistic and basic could make use of more visually interesting colour choices, layout choices, etc.
Under the 'Content' menu, it defaults to having a landing page for all L1 and L2 category pages. Meaning as long as the broader content category has a sub-category, it still creates a separate landing page. In my team's case, this often creates blank pages, as we only fill out the page at the lowest sub-category (L3).
Hyperlinks are traditionally shown as blue, however, this results into very monotonously blue pages in cases where a lot of information is being linked.
I am confident that Atlassian can come with additional and innovative macros and functions to add value to Confluence. In 6 months, Atlassian transformed a good collaborative tools into a more comprehensive system that can help manage projects and processes, as well as "talk" with other Atlassian products like Jira. We are in fact learning more about Jira to evaluate a possible fit to complement our tool box.
Bamboo offers solid usability for teams looking for an integrated, scalable CI/CD solution, especially those using Atlassian tools. Its interface is intuitive for existing Atlassian users, and its focus on deployment automation makes it a strong option for continuous delivery. However, its complexity and cost may pose challenges for small teams or those new to CI/CD. Overall, Bamboo’s usability shines in environments where ease of integration and streamlined workflows are prioritized. Still, it may require more effort for teams unfamiliar with its setup or without dedicated resources.
Great for organizing knowledge in a hierarchical format. Seamless for engineering and product teams managing software development. Helps in formatting pages effectively, reducing manual work. Tracks changes well and allows for easy rollbacks. Granular controls for who can view/edit pages. Search function is not great which needs improvement. Hire some google engineers
We never worked against the tide while using Confluence. Everything loads considerably fast, even media components like videos (hosted on the platform or embed external videos from Youtube, for example). We are not using heavy media components a lot, but in the rare occasion we happen to use one we have no problems whatsoever.
Bamboo is a fairly small product but having said that it was fairly easy to get assistance. Especially for the small to easy things. Anything large or fairly complex was an issue finding detailed answers for. This caused a lot of trial and error on our part to try to find a solution.
This rating is specifically for Atlassian's self-help documentation on their website. Often times, it is not robust enough to cover a complex usage of one of their features. Frequently, you can find an answer on the web, but not from Atlassian. Instead, it is usually at a power user group elsewhere on the net.
We selected Bamboo because its capabilities to integrate with other Atlassian products specially Jira Software, Bitbucket and in some useful scenarios with Confluence. Also, we found these pros important for us: great user interface, easily agent deployment, Docker compability, simply to maintain / manage, and straightforwardly integration with different notification platforms
We chose Atlassian Confluence over SharePoint because it's much more user-friendly and intuitive. Atlassian Confluence makes collaboration and knowledge sharing easier with its simpler interface and better search. While SharePoint can be powerful, it often feels clunky and complex, making it harder for our team to actually use it.
It helped us achieve the Continuous Deployment and Continuous Integration goals for our applications, a huge milestone that saved a lot of time for developers in making the builds and deployments and saved time for QA in running the automated tests.
Helped with DevOps: we moved the formal approval from the email to the system and allowed the approver to actually push the button for the production deployments.
Biggest positive impact of using Bamboo is that it improved our response time to customers and increased the frequency of our deliveries to them.