We just raised a $30M Series A: Read our story

Atlassian Confluence OverviewUNIXBusinessApplication

Atlassian Confluence is #1 ranked solution in top Knowledge Management Software, #2 ranked solution in top Corporate Portals, and #2 ranked solution in top Enterprise Social Software. IT Central Station users give Atlassian Confluence an average rating of 8 out of 10. Atlassian Confluence is most commonly compared to Microsoft Teams:Atlassian Confluence vs Microsoft Teams. The top industry researching this solution are professionals from a computer software company, accounting for 23% of all views.
What is Atlassian Confluence?

Project management is easy with Atlassian's Confluence as your single source of truth. It integrates with JIRA so you can easily add context to your projects in one central location. Create and track issues & product requirements, publish release reports, track release progress, and more when you connect Confluence and JIRA. Confluence allows you to create, share, evolve, and capture your team's project documentation so you can collaborate better, smarter, and as a team.

Confluence also organizes your powerful repository of information, opinions, and knowledge to help you answer questions, create how-to docs, and possibly identify the next big thing. Logical and consistent management of knowledge and a powerful search engine ensure that you can always find the right content, when you need it most. Share, organize, and discover content all in one platform.

Confluence has multiple deployment options to provide the flexibility your organization needs.

Cloud is a fully hosted service for customers who want to iterate quickly and have us take care of managing the infrastructure.

For customers who need to run our applications behind their firewall, we have Server and Data Center options. Server delivers greater capacity for a larger user base and gives you more control, allowing you to remain compliant with your enterprise IT, security, IP and privacy policies. For our largest customers, Data Center provides all the capability of our Server option, along with high availability, instant scalability and performance at scale.

Atlassian also offers premium support and strategic services for enterprise customers. Technical Account Managers are cross-functional technical advisors providing proactive planning and strategic guidance across your organization. Premier Support goes above and beyond our standard offerings to give you account-wide support from a team of senior support engineers.

Atlassian Confluence is also known as Confluence.

Atlassian Confluence Buyer's Guide

Download the Atlassian Confluence Buyer's Guide including reviews and more. Updated: November 2021

Atlassian Confluence Customers

Facebook, Skype, Microsoft, NASA, Netflix, Adobe, Bonobos, LinkedIn, Pfizer, Citi.

Atlassian Confluence Video

Pricing Advice

What users are saying about Atlassian Confluence pricing:
  • "The price of the on-premises data center version is too expensive."
  • "For us, it's free to use. We don't pay any licensing."
  • "The issues I have with the pricing are in respect to the add-ons."
  • "When you purchase this solution you get some support."

Atlassian Confluence Reviews

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
WiseCat
Enterprise Architect, CISSP at a tech services company with 1,001-5,000 employees
Real User
Top 5Leaderboard
Good usability, helpful community support, and facilitates well-structured documentation

Pros and Cons

  • "It has a very intuitive user interface, which every user able to manage the basic functionality of a PC will be able to work with and produce quite satisfactory results."
  • "Atlassian should rethink its withdrawal of the self-hosted version of the product. They only offer cloud-based service or the "datacenter-edition", which is quite expensive for small companies and private users."

What is our primary use case?

I primarily used this solution for IT documentation and documenting ISMS based on ISO 27001.

With the Confluence Wiki, I implemented quite a series of successful IT and Security Documentation projects. Confluence was my preferred product when starting any collaboration project that had to produce comprehensive, centrally organized, and highly usable documentation.

I worked on several projects that implemented an ISMS, based on the ISO 27001 standard, which mandates a "documented ISMS". I introduced Confluence as the tool to be used for that documentation.

I used Confluence as the "self-hosted" server in VMs or on MiniPCs running Linux. I always added backup methods, so the HA functionality of the much more expensive "datacenter-edition" was never needed. The largest environment I worked in had 100+ active authors, but typically I would work with the 10- or 25-user license, which are both quite affordable even for small customers and where the server resources are manageable (From two to four virtual cores and 4-16GB RAM will do fine).

How has it helped my organization?

This solution worked fine until Atlassian decided to force everybody into the cloud.

The most mentionable improvement is that documentation with Confluence gains a much better structure. Instead of hundreds of .doc and .xls files roaming the network shares and C: drives of team members, once you get Confluence set up, spend a few hours with all designated authors to define a few guidelines on how pages should look, be interlinked, and how to generally use the tool, the productiveness of creating and improving documentation is phenomenal!

The key is to take the mentioned few hours, get everybody together and produce a "style guide", for want of a better word, about how to use Confluence. Then agree on the top-level structure of your documentation and if everybody accepts this and uses it in their work, all is fine.

My recommendation is to meet for an hour every other week with those who work the most with the tool and fine-tune said "style guide" and the structure. This will help everybody to keep being motivated and to produce the best results. Also in such meetings, ideas about add-ons can be discussed and their integration planned.

What is most valuable?

Atlassian Confluence is a very good and seasoned Wiki Solution.

First and foremost, I want to mention its top-notch usability. It has a very intuitive user interface, which every user able to manage the basic functionality of a PC will be able to work with and produce quite satisfactory results.

There is a big and responsive community to help with questions and so far, Atlassian is still doing a good job to help.

Also, there are add-ons from various sources, which can be integrated with the product quite easily and have good chances to function together as a whole, like intended.

Another thing worth mentioning is the very good import and export functionality. You can just use Copy-Paste on a website or a document and Confluence will in most cases manage to reproduce the content quite recognizably. Export not only as XML, to be able to reimport, but also, PDF and Word DOCX work quite well. They can be further improved, speaking from personal experience with PDF files, by adding a few add-ons for formatting, page heading, and such.

Oh, and last but not least the flexibility should be mentioned. If for any reason there is the need to change the structure of the contents, say to move a branch of pages from one top-level area to another, just copy them or export them and re-import them in their own area. Mostly, that works without a glitch (exceptions prove the rule) and even cross-area-links will continue to work. For more complicated restructuring, one can always use the XML-Export and load it into an XML-Editor. Of course, that´s for people who can read and understand XML structure.

What needs improvement?

Atlassian should rethink its withdrawal of the self-hosted version of the product. They only offer cloud-based service or the "datacenter-edition", which is quite expensive for small companies and private users.

I have been using and recommending Atlassian Confluence for more than four years now, and never had to regret it until the end of 2020, when they suddenly got this cloud madness.

Not only does the cloud version come nowhere near the responsiveness of the self-hosted version (which is a matter of course, as self-hosted servers are within the LAN with single-digit milliseconds of round trip time, whereas cloud-hosted servers will always have 20+ ms), but also it requires a customer to entrust their data to a third party, which is in many cases a no-go.

The only way out would be to buy the "datacenter edition" and thus spend a whole lot more money on the product. This may be what Atlassian intended in the first place and if so, shame on them.

With that, I will no longer recommend the product, as I am opposed to the cloud-first hype. Our data should be our own and we should be free to decide where we store them.

For how long have I used the solution?

We have been using Atlassian Confluence for approximately five years.

What do I think about the stability of the solution?

No complaints that I know of - unless some admin shoots the underlying VM (has been heard to happen), confluence is just rock-solid. To be sure: It needs some resources, and if the VM starves of memory or CPU, performance and stability will suffer.

What do I think about the scalability of the solution?

As I said, the largest environment i was working with at a customer has 100+ authors and I imagine plenty of pages and other content - sadly I do not know the exact figures - but we never had reason to complain in our project which only consisted of 12 people actively using Confluence. So I guess scalability should not be an issue.

Which solution did I use previously and why did I switch?

Prior to Confluence, I tried working with Microsoft SharePoint. Well, there were those sad tries, and my advice is to forget it.

SharePoint may have advantages when it comes to organize and share files, but the ease and intuitive way to create structured documentation just is not there.

And as a sidenote: When working on projects we would oftentimes edit a page in confluence with three or four of us concurrently updating table entries or text segments. Very seldom have I experienced problems with allowing concurrent edits and in my mind never incorrect merging of inputs. Again, that is true for the on-premises self-hosted version, in the cloud that does not work quite as well.

And why do I point this out: Have any of you tried to edit a word document in MS Teams concurrently? ... it produces quite funny effects but in my opinion cannot be trusted, really.

How was the initial setup?

The cases where I set up the server myself were straightforward and went without any glitch along the documented steps.

What about the implementation team?

Up until now I only had inhouse admins implement the servers, they did it noiselessly and with satisfying results.

What was our ROI?

Erm. ROI. Hm. Can anybody please call the finance guy? ...

What's my experience with pricing, setup cost, and licensing?

Well, that´s difficult now. Until the end of 2020, using a self-hosted server, have one of your IT-Admins set it up, costs $10 a year for the 10-Author license.

Nowadays? Don´t use it. The price of the on-premises data center version is too expensive.

Which other solutions did I evaluate?

To be honest, after being introduced to Confluence by a colleague all those years ago, I did not evaluate any other option in earnest.

Recently, I started looking at Tiki Wiki, which is a fully OpenSource alternative, but I haven´t gotten around to installing it or using it in a new project.

I would not consider alternatives but for the policy of Atlassian. Such a good product should run in every datacenter. NOT in the Clouds, though.

What other advice do I have?

My advice for everybody is to flame Atlassian into re-providing the self-hosted server version!

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
DM
Delivery Lead at Cyma
Real User
Top 20Leaderboard
Good notifications, great third-party add-ons and very stable

Pros and Cons

  • "The integration's very good. You still have integration with lots of third party products, and it's very good."
  • "This is kind of by design, however, the lack of control in terms of editing the page to make it look the way you want it to look is an issue. It would be nice if there was more flexibility there."

What is our primary use case?

We primarily use it as a knowledge management tool for all of our consultants, which are architects.

What is most valuable?

The whole solution is really great. I appreciate the ability to create content, link content, and then search for that content when I need to. 

I love all of the add-ons the solution offers. You get the base product, and then you can plug in a ton of third-party apps. There's a whole ecosystem of third-party products you can add in if there are any features that may be missing on Confluence itself. That's really great. 

There are very good notifications and links. You can subscribe to a page, and whenever that page gets edited, you're notified of a change on that page.

I suppose just the whole structure and organization is what I really like about Confluence. You have at least 500 odd pages. The way it's structured, again, to speed up the ability to find stuff, is phenomenal. 

The self-service capabilities are helpful. Anyone can create content. We do, in fact. It's not one person running lots and lots of pages of content, it's everyone. You can self-service, update, and change things yourself, which is good. It's a great collaboration endeavor. We are a team of 15 people and we'll leverage the content we've created previously. The ability to collaborate on the content is quite critical to us.

The integration's very good. You still have integration with lots of third party products, and it's very good. 

What needs improvement?

We've used a lot of time in correcting our knowledge in this product. Can't really think of a negative feature of the product.

This is kind of by design, however, the lack of control in terms of editing the page to make it look the way you want it to look is an issue. It would be nice if there was more flexibility there.

It's only a very constrained format you can use. You cannot change the font and you can't really make them smaller. It is by design, but it doesn't like people playing with those aspects. It's probably gone a bit too far. The inability to format the layout of a page is an issue for us.

The logic for searching for pages is a bit off. I assumed it would be very smart in terms of looking at the content on your page and looking at what people clicked on. I assumed it would be like Google in that it would know what people clicked on previously when they were looking for this keyword, what page do they click on, et cetera. It doesn't. I found some detailed explanation of exactly how the search works and it's quite disappointing. It's very basic. Search largely depends on the title of your actual document. It doesn't look at the words in the document, and doesn't look at the search history, in terms of how people pick pages.

It turns out that the searching algorithms are very basic. When I assumed the product was bad, it was actually due to the fact that most of the knowledge management tools have very smart searching logic. This one doesn't. 

For how long have I used the solution?

I've been using the solution for probably less than a year. It hasn't been too long.

What do I think about the stability of the solution?

The solution is reliable. I haven't seen a single bug or issue with the product. It's very stable. 

What do I think about the scalability of the solution?

We have about 15 users on the solution currently.

Which solution did I use previously and why did I switch?

As a company, we use Microsoft Teams. A lot of our customers say, "Oh, I know, we've got the same features in Microsoft Teams." However, that really isn't the case. Usually, if you're in a Microsoft shop, you would try and use all the Microsoft products. This is one space where Microsoft Teams doesn't cut it. We're using the Confluence instead.

How was the initial setup?

The initial setup is very, very good. It's not complex it all. It's very straightforward and they make it very easy.

The entire setup isn't an intricate process. We didn't have to pour over documentation to try and figure things out. We just followed our instincts and it worked out quite well.

What about the implementation team?

We handled the implementation ourselves. We didn't need any assistance from consultants or integrators.

What's my experience with pricing, setup cost, and licensing?

For us, it's free to use. We don't pay any licensing.

What other advice do I have?

We don't have a business relationship with Atlassian. We're just customers.

We're using the latest version of the solution.

This solution is highly recommended. If you're looking for a product in this space, this is the best. We had another really good tool, however, we find Confluence does the same and a whole lot more. I'd say in the knowledge management space, as far as we've been doing our business, and our job is to find tools for organizations, I'm convinced that this is the top product in this space.

Overall, I'd rate the solution nine out of ten. My one issue is the search capabilities. Otherwise, it's pretty perfect.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Learn what your peers think about Atlassian Confluence. Get advice and tips from experienced pros sharing their opinions. Updated: November 2021.
552,695 professionals have used our research since 2012.
BK
CEO & CPO at a tech services company with 11-50 employees
Real User
Top 20
Confluence is a great solution for early-stage documentation and communication.

Pros and Cons

  • "With respect to our experiences with Confluence, we haven't had any issues."
  • "It would be interesting if they had graphical templates that allowed typical agile ceremonies to be documented better."

What is our primary use case?

We mainly used Jira for backlog management within IT development landscapes. We used Confluence for early-stage documentation and communication within and across teams.

Since we worked mostly with large enterprises, they typically install and host any server-based solutions on their own.

What is most valuable?

The interesting thing is the connector between Jira and Confluence (it works wiki-like and provides a deep-connection with links between both systems). The alternative is to run for early-stage backlog-items in immature state a separate wiki-instance that would not feature the proper linkage of backlog-entries automatically.

What needs improvement?

With respect to Confluence, it would be interesting if they had graphical templates that allowed typical agile ceremonies to be documented better. For example, one of the agile cadences that we regularly run is risk roaming. Confluence, as of now, doesn't provide any kind of graphical support for creating a two-by-two portfolio matrix design or even something similar. Basically, Confluence is heavily text-based. Some of my customers have actually started to tweak the system a bit and implement workarounds. On the screen, you can make it look as if it is a two-by-two portfolio; however, if there were templates provided, that would be great. The basic graphical templates that are used regularly in management would be fine. It would be great to see them supported in the future. 

In regards to Jira, it would be nice if they had two-dimensional features for backlog support. At the moment, backlog management is always a flat, one-dimensional list but our customers actually prefer having the opportunity to have that read out in a graphical fashion as well. That way, there's so much more overview and they can cluster smaller backlog items that come as a bunch. It just provides much more clarity.

Jira still seems to have issues on modelling Kanban-systems - as far as I know it still doesn't support the so-called "commitment point" (i.e. creating a non-romovable time-stamp when moving a ticket onto a board) helpful in creating transparency about start- and end-time of performing an activity — similar to signing a document in writing.

Think of it this way: if you take an item into a boardroom, it must be noted and signed. It should be done in pencil where the data could be erased later on, rather, it should be stamped — basically, you are not losing the data again. That is still an issue with these systems. That's one of the reasons why many teams who want to run Kanban methodology don't want to use Jira. They tend to use other software, which is able to do these sorts of things. 

For how long have I used the solution?

Until 2018, I was employed with an applier of Atlassian solutions. Within that context, I used Confluence for a year. I have used Jira 2012—2018 as an end-user myself. From then onwards, I was more of a consultant to other companies implementing and using similar solutions. In short, if you count only end-usage, then it's 6 years with Jira and one year with Confluence.

What do I think about the scalability of the solution?

With respect to our experiences with Confluence, we haven't had any issues; however, we definitely have had issues within the Jira environment back in 2014.

Scalability issues should have been fixed by now - they arose back in 2010-2014 at one of the largest enterprise implementations for multi-1.000s of concurrent users on the system, causing the system to operate very slow - I would expect that by 2020 this is treated accordingly to make the system scale without loss of performance. 

How are customer service and technical support?

I have not personally contacted Atlassian's technical support. It was always routed via the respective IT staff, which I was not involved with.

How was the initial setup?

I was not involved with technical administration or the implementation procedure from an IT infrastructure team perspective. For this reason, I can't speak for individual customers.

What's my experience with pricing, setup cost, and licensing?

The problem with the pricing model is not so much the price for the Atlassian basic software itself; the issues I have with the pricing are in respect to the add-ons. The problem with add-on pricing is that it typically is always calculated based on the amount of basic Confluence or Jira licenses. Since some of the add-ons will only get used by a very limited number of users, having to pay for the full implementation (for all the people using Confluence or Jira), seems like an unfair pricing model. It also prohibits the usage of certain add-ons, too. Certain add-ons from a functionality-perspective are much more exclusive to only a few users. That pricing model should be reviewed and potentially edited or amended to make it more flexible.

What other advice do I have?

On a scale from one to ten, I would give this solution a rating of eight. If they added the graphical templates, I would give them a higher rating.

To me, as an end-user, the topical templates are pretty basic. Under the current conditions, since COVID-19, our teams have tried to become more virtual in their collaboration model. The collaboration model that we had installed before, face-to-face, couldn't be transferred, which is kind of a pity because the graphical features are missing.

Which deployment model are you using for this solution?

On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer: Integrator
Lindsay Fifield
Customer Success Manager at LogiGear Corporation
Vendor
Top 20Leaderboard
Great organizations capabilities, perfect for non-technical users, and very stable

Pros and Cons

  • "It's extremely intuitive."
  • "The UI is good but bland. It could be updated a bit to make it more modern and interesting to look at."

What is our primary use case?

We are a remote company at this point. We use it to collaborate on different initiatives within our interior and marketing teams. It's kind of our one-stop-shop to house our collateral and sales information. It covers pretty much anything and everything we need and everything our marketing teams would need as well.

What is most valuable?

We really like how it organizes everything. I don't know if it's because of the ability to create different pages or not, however, everything is very organized. It's easy to differentiate different materials based on the project and navigate to them. The solution makes it so it's very easy to navigate and very easy to search. 

It's extremely intuitive.

The solution is great for non-technical users. You don't have to have a big technological background to work with it effectively. I myself am not very technical and I can get around it without much difficulty.

What needs improvement?

The UI is good but bland. It could be updated a bit to make it more modern and interesting to look at.

For how long have I used the solution?

I've only been using the solution since January of 2020, so it's been about six months now.

What do I think about the stability of the solution?

The stability of the solution is great. There are no issues whatsoever there. I haven't found that it crashes or freezes. There aren't bugs or glitches that affect the way it functions. I would say that it is very consistent and reliable.

What do I think about the scalability of the solution?

I assume the scalability of the solution is good. My company has used it for several years now. We've been growing in that time and we haven't had any kind of stability issues and we've never felt like the solution has gotten too small to meet our needs. It grows with us. We've been able to utilize it as we've needed, as we've grown. It seems to scale nicely.

How are customer service and technical support?

I've never had a need to reach out to technical support, so I can't speak to the quality of its services.

Which solution did I use previously and why did I switch?

We also use Salesforce as a project management tool. They aren't really the same, however, we do use the two in tandem.

What's my experience with pricing, setup cost, and licensing?

I don't know what the licensing costs for the solution are at this time.

What other advice do I have?

We're Atlassian customers. I'm just the customer success manager, so I'm not on the technical or the testing side.

I'm not sure which version of the solution we are on, however, I believe it to be the most up to date version that is currently available.

I'd advise other organizations, if they decide to implement the solution, to really utilize it. If you plan to use it as a really strong collaborative tool, ensure that everyone using it has access to the required documents and that they utilize it on a consistent basis. I've found the most benefits from using it when I'm consistent with it. You really need to update it as often as you update your Salesforce. That might mean daily updating, depending on how you use it.

I'd rate the solution eight out of ten. If it had better UI, I might rate it a bit higher.

Which deployment model are you using for this solution?

Private Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Michael Peterson
GM Technology at a energy/utilities company with 51-200 employees
Real User
Top 20Leaderboard
Easy to use out-of-the-box templates satisfy the majority of common use cases.

Pros and Cons

  • "It is easy to use."
  • "There is a good library of templates for a wide range of needs."
  • "It integrates well with other Atlassian products"
  • "The product should have a workflow with approvals out-of-the-box."

What is our primary use case?

Every project and every initiative we start gets a Confluence site to track artifacts that are created related to that initiative. For example, we will use it for a knowledge base and for general documentation. We collect all of our meeting minutes, action lists, and so on. It is grouped in scenarios for reference, et cetera.  

What is most valuable?

I think it is easy to use. There are a large number of out-of-the-box templates, which can satisfy the majority of use cases. If those templates do not quite cover what you want them to do, you can tweak the templates so you can create your own just so you end up with standardized content look and feel. It integrates well with the other Atlassian products, like the Jira software, which we use for our software development teams.  

Overall I am pretty satisfied with it. We like the user interface and it is similar to the Jira software as well which makes it very familiar.  

What needs improvement?

Workflows is an area where it could be improved. Out-of-the-box, it does not have a good workflow solution, which is a bit odd given that there is a good workforce solution in Jira software. We had to purchase a workflow management tool off the marketplace called Kamala and that probably should not have been necessary. So, they could probably do with a bit of development on the workflows front to include a better solution out-of-the-box, but other than that, not a lot needs to be improved.  

For how long have I used the solution?

Personally, I have been using Confluence since around 2013. About seven years.  

What do I think about the stability of the solution?

Confluence does not have any bugs, glitches that I can recall.  

What do I think about the scalability of the solution?

The scalability is pretty good.  

How was the initial setup?

The installation and setup for Confluence itself is relatively straightforward. There is good online documentation for it as well. The templates help make easy work of the design and site creation.  

What other advice do I have?

I would recommend Confluence, especially for anyone that is using other Atlassian products. It is a simple, additional, license to get the solution and it integrates really well with the other products in the Atlassian family.  

On a scale from one to ten (where one is the worst and ten is the best), I would rate Confluence overall as a product as an eight-out-of-ten. I would not rate it higher because like all the Atlassian products, there are certain things I think the product should have out-of-the-box without you needing to go to the marketplace. For example, it does not have an approvals type of workflow. If you want to create content and have other people review and approve it before it gets published that should be available. I would think that is something that it should have out-of-the-box.  

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Other
Disclosure: I am a real user, and this review is based on my own experience and opinions.
SS
System Engineer at a insurance company with 1,001-5,000 employees
Real User
Top 20
Easy to use and set up, includes Wiki software, the support is good, but the need better third-party integration

Pros and Cons

  • "What I like the most is the Wiki software that comes with Atlassian Confluence."
  • "I would like to see integration with Slack."

What is our primary use case?

In multiple organizations, we have been using Atlassian Confluence as a knowledge base, and for development. Our developers use it alongside Jira.

What is most valuable?

What I like the most is the Wiki software that comes with Atlassian Confluence.

The interface is good and it's pretty easy to use. Most developers have some experience with Jira, which makes it pretty easy for people to pick up. We don't usually need to provide them a string.

What needs improvement?

They can easily take on some of the features from Slack. 

They could try and copy Slack more and bring them into the market a bit quicker. That would be helpful for them.

I would like to see integration with Slack.

There could be improvements with the app ecosystem. For example, if we look at Teams, there is now an entire ecosystem. With Teams, you can essentially install any apps and do any integrations. Third-party, similar to Microsoft.

It's more about integrations with third parties. That is also something that could be better.

I think it can be more competitive, considering the competition they are now going to get from Slack and Teams. For example, if you look at Microsoft Teams, Microsoft is providing 365 for free with Slack.

For how long have I used the solution?

I have been using this solution for approximately seven years.

What do I think about the stability of the solution?

We have not had any issues.

What do I think about the scalability of the solution?

We have 1100 users.

How are customer service and technical support?

The customer support is pretty good. If you reach out to them, they are very helpful.

How was the initial setup?

The initial setup is pretty straightforward, I have never had any issues.

What's my experience with pricing, setup cost, and licensing?

When you purchase this solution you get some support.

Which other solutions did I evaluate?

Jira and Confluence go hand in hand. If it's for development, and if people have money to pay for one product only, they usually end up purchasing Jira, and not Confluence. 

But at the end of the day, it's an ecosystem. It really depends on how much you want to integrate and how much you want to dive into it.

What other advice do I have?

It really depends on what ecosystem they invest in and what they're looking for.

You have to look at the use case and if you already have an application in your ecosystem which is fit for purpose, you have to ask yourself, why you want to go out and pay for another product?

I would rate this solution a seven out of ten.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PG
Business Analyst at a comms service provider with 10,001+ employees
Real User
A one-stop shop for all project documentation

Pros and Cons

  • "It is just the fact that it is a one-stop shop for all project documentation. It is compared to storing things in files and directories and stuff like that. It provides the overall usability and accessibility of many projects and documents in one area."
  • "It would be good if they can continue working towards making documentation and editing as quick and easy as possible. It has got a lot of capability, but I don't know how to use it. I don't find some of the things that intuitive. Sometimes, it doesn't seem obvious to me how to use it, but it is like learning any new tool. You actually need to get trained on the tool to get maximum out of it."

What is our primary use case?

We have got our own private Confluence set up. In our department, we use Jira and Confluence a lot. These are our in-house go-to tools for managing the agile ways of working. We sort of follow a bit of both models: traditional and agile. We follow the traditional waterfall model outside of Confluence and Jira, so that's more like requirements, specifications, and documents. There's another team, with which I haven't been that involved, that writes user stories and allocates tasks in Jira. They use it quite heavily.

We use Jira more for agile type processing, like for Kanban boards and all that sort of stuff and allocating work tasks and two-week sprints. It supports the actual agile process. Jira is much more focused on the process of delivery.

What is most valuable?

It is just the fact that it is a one-stop shop for all project documentation. It is compared to storing things in files and directories and stuff like that. It provides the overall usability and accessibility of many projects and documents in one area. 

What needs improvement?

It would be good if they can continue working towards making documentation and editing as quick and easy as possible. 

It has got a lot of capability, but I don't know how to use it. I don't find some of the things that intuitive. Sometimes, it doesn't seem obvious to me how to use it, but it is like learning any new tool. You actually need to get trained on the tool to get maximum out of it.

For how long have I used the solution?

I have been using this solution for the last two to three years.

What do I think about the scalability of the solution?

It is scalable.

How are customer service and technical support?

We have our own engineers.

How was the initial setup?

The initial setup was straightforward.

What other advice do I have?

I would rate Atlassian Confluence an eight out of ten. It provides everything for our use cases.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Naresh Rayakwar
Tech Mahindra Total Duration14 yrs TitleTech Lead for KPN Project at a computer software company with 10,001+ employees
Real User
Top 5
Useful for documentation design, but drawing features could be improved

Pros and Cons

  • "The most valuable features is its design documentation abilities."
  • "Some aspects of the drawing perspective could be improved. When we upgrade a design and make technical architecture drawings to publish, we still use Visio first and then copy and paste it. If this feature were available on Confluence, it would be a useful tool."

What is our primary use case?

Our primary use case is for documentation. We used to maintain other documents in another location, but we moved to Confluence. We use it for the design documentation perspective, not for the analytics perspective. 

What is most valuable?

The most valuable feature is its design documentation abilities. 

What needs improvement?

Some aspects of the drawing perspective could be improved. When we upgrade a design and make technical architecture drawings to publish, we still use Visio first and then copy and paste it. If this feature were available on Confluence, it would be a useful tool. 

For how long have I used the solution?

I have been using this solution for more than two years. 

What do I think about the stability of the solution?

This solution is stable and well-integrated with Jira

What do I think about the scalability of the solution?

This solution is scalable. 

How are customer service and support?

I have never directly contacted Atlassian technical support. 

Which solution did I use previously and why did I switch?

I use SharePoint as well, mainly for the version control because I still need to prepare the document in Word and Visio and then load it to SharePoint

How was the initial setup?

The initial setup, the installation, was managed by someone else. 

What about the implementation team?

I implemented through an in-house team of three developers and engineers. They maintain both Confluence and Jira

What's my experience with pricing, setup cost, and licensing?

I believe we have the Enterprise license with Confluence. 

What other advice do I have?

I recommend Confluence to others. There are about 400 people in my company using this solution. However, if you are doing extensive drawings or looking for the version-control perspective, then I would caution you and suggest looking at another solution. 

I would rate Confluence a seven out of ten. 

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate