Brightspot CMS - Private Offer Only
BrightspotReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
43 reviews
from
External reviews are not included in the AWS star rating for the product.
Publishing with Purpose: Brightspot’s Role in Connecting Families Worldwide
What do you like best about the product?
Scalability and flexibility are key strengths of Brightspot, as it manages large-scale publishing and multi-site operations smoothly.
We rely on Brightspot to publish content for our RootsTech Conference, which serves more than 11 million attendees over a four-day period. Additionally, we operate a global help center and a blog site available in nearly 50 languages. We also oversee 50 separate localized websites for our FamilySearch Centers.
We rely on Brightspot to publish content for our RootsTech Conference, which serves more than 11 million attendees over a four-day period. Additionally, we operate a global help center and a blog site available in nearly 50 languages. We also oversee 50 separate localized websites for our FamilySearch Centers.
What do you dislike about the product?
The most frustrating aspect of Brightspot is the restricted access to new features within the product. Since we use a headless configuration that depends on custom development for implementation, innovations introduced to Brightspot’s platform do not always make their way to non-standard builds. As a result, self-hosted teams are often left without the latest tools and efficiencies.
This situation frequently forces us to develop or replicate features on our own, which not only slows our pace of innovation but also adds to our maintenance workload.
This situation frequently forces us to develop or replicate features on our own, which not only slows our pace of innovation but also adds to our maintenance workload.
What problems is the product solving and how is that benefiting you?
Distributed Content Publishing across Teams, Locations, and Languages
Managing content creation and publishing across dozens of global FamilySearch Centers, each with unique offerings and audiences, is complex and hard to scale. Brightspot provides a centralized CMS with multi-site capabilities, allowing local teams to publish their own content while maintaining governance and brand consistency. The benefit is enabling local centers to operate independently while still aligning with FamilySearch’s global standards — reducing bottlenecks and empowering community engagement.
Unified Management of Diverse Content Types
We need to manage blogs, help articles, event content (like RootsTech), and localized pages — all with different formats and workflows. Brightspot supports a wide range of content types and workflows in one platform, streamlining editorial processes. This means we need only one system to manage everything — reducing training time, simplifying operations, and improving content consistency.
Managing content creation and publishing across dozens of global FamilySearch Centers, each with unique offerings and audiences, is complex and hard to scale. Brightspot provides a centralized CMS with multi-site capabilities, allowing local teams to publish their own content while maintaining governance and brand consistency. The benefit is enabling local centers to operate independently while still aligning with FamilySearch’s global standards — reducing bottlenecks and empowering community engagement.
Unified Management of Diverse Content Types
We need to manage blogs, help articles, event content (like RootsTech), and localized pages — all with different formats and workflows. Brightspot supports a wide range of content types and workflows in one platform, streamlining editorial processes. This means we need only one system to manage everything — reducing training time, simplifying operations, and improving content consistency.
Best-of-breed CMS solution
What do you like best about the product?
Brightspot's thorough analysis of our existing platform and thoughtful consultation to identify how to migrate our existing content and integrate our content workflows has made this CMS switch (almost) painless. Their customer support is first-rate!
What do you dislike about the product?
Coming from a homegrown solution, workflows in Brightspot tend to require a few more clicks than our custom solution.
What problems is the product solving and how is that benefiting you?
Brightspot is helping us modernize our existing content workflows to find new synergies and ideas within our organization.
Brightspot: Not Just Another Dot in the CMS U-Verse
What do you like best about the product?
One of the best things: we’re less dependent on devs for day-to-day product management tasks — PMs can do a lot more without waiting in a backlog.
Strong customization across the board: granular user permissions, custom workflows, flexible form content and content types let us tailor the CMS pretty tightly to our process.
The support team is genuinely helpful — when issues come up, they don’t just point you at docs; they jump in and assist.
Ability to impersonate users is a huge win: it helps us debug permissions / view problems exactly as the user sees them.
Bulk content editing/updating is powerful — saves tons of time when we need to roll out changes across content items or users.
Revision history is great; being able to go back, compare versions, restore content helps with accountability + recovering from mistakes.
Flexibility to adapt for evolving needs — even when new types of content or workflows come up, much of Brightspot can be extended rather than rebuilt.
Strong customization across the board: granular user permissions, custom workflows, flexible form content and content types let us tailor the CMS pretty tightly to our process.
The support team is genuinely helpful — when issues come up, they don’t just point you at docs; they jump in and assist.
Ability to impersonate users is a huge win: it helps us debug permissions / view problems exactly as the user sees them.
Bulk content editing/updating is powerful — saves tons of time when we need to roll out changes across content items or users.
Revision history is great; being able to go back, compare versions, restore content helps with accountability + recovering from mistakes.
Flexibility to adapt for evolving needs — even when new types of content or workflows come up, much of Brightspot can be extended rather than rebuilt.
What do you dislike about the product?
Such deep customization means managing changes can become a headache — lots of moving parts, high chance of unintended side-effects.
Sites & settings don’t save history of changes, so it’s tough to trace who did what and when.
The tech stack can feel heavy; maintaining/updating underlying systems (dependencies, libraries, frameworks) can be painful.
The schedule build-out (for our radio shows) is still giving us grief that don’t mesh cleanly with the system’s scheduling tools.
Platform upgrades are a bear when you have a small team already focusing on other priorities.
Sharing content across sites is not seamless; duplication, syncing, or coordinating changes across multiple site instances has friction.
Documentation isn’t always up to date or detailed enough for some of the more complex custom workflows.
Sites & settings don’t save history of changes, so it’s tough to trace who did what and when.
The tech stack can feel heavy; maintaining/updating underlying systems (dependencies, libraries, frameworks) can be painful.
The schedule build-out (for our radio shows) is still giving us grief that don’t mesh cleanly with the system’s scheduling tools.
Platform upgrades are a bear when you have a small team already focusing on other priorities.
Sharing content across sites is not seamless; duplication, syncing, or coordinating changes across multiple site instances has friction.
Documentation isn’t always up to date or detailed enough for some of the more complex custom workflows.
What problems is the product solving and how is that benefiting you?
Brightspot is helping us reduce bottlenecks with our development team by giving editors and producers more control over day-to-day content updates. Instead of waiting for engineering to make simple changes, our teams can move faster and focus dev resources on other projects.
The platform’s customization options — from workflows and permissions to content types — mean we can adapt the CMS to fit our editorial and business processes. That flexibility makes it easier to support different teams, brands, and content needs under one system.
Brightspot also solves the problem of content reliability and accountability. Features like bulk updates and detailed revision history make it easier to manage large volumes of content with confidence and support editorial users who face issues, while the ability to impersonate users helps us quickly troubleshoot issues.
Finally, the support team has been a key benefit: Their responsiveness and problem-solving ensure that when we do hit a wall, we’re not stuck for long.
The platform’s customization options — from workflows and permissions to content types — mean we can adapt the CMS to fit our editorial and business processes. That flexibility makes it easier to support different teams, brands, and content needs under one system.
Brightspot also solves the problem of content reliability and accountability. Features like bulk updates and detailed revision history make it easier to manage large volumes of content with confidence and support editorial users who face issues, while the ability to impersonate users helps us quickly troubleshoot issues.
Finally, the support team has been a key benefit: Their responsiveness and problem-solving ensure that when we do hit a wall, we’re not stuck for long.
New to Brightspot
What do you like best about the product?
We recently transitioned our news media site to the Brightspot CMS. Since we’re operating in a headless environment, we’re not taking advantage of every capability Brightspot offers, but we’ve found it to be both highly user-friendly and easily customizable.
What do you dislike about the product?
Dislikes are the ECT model. Unfortunately, due to budget we chose this route, but should’ve gone with the Java model for more customization.
What problems is the product solving and how is that benefiting you?
I’m not the right person to answer that question.
Best CMS I’ve used so far!
What do you like best about the product?
The easy to use user interface, ability to customize the CMS without having to dig into the backend code. It is much appreciated from a CMS user who is also a front end developer.
What do you dislike about the product?
Out of the box, I’d like to be able to schedule and archive pages. We had an old CMS we used to use by Optimizely and having the ability to schedule archive pages was such a plus.
What problems is the product solving and how is that benefiting you?
It’s solving a lot of our issues such as not needing to submit a ticket to our IT to do content changes.
Brightspot CMS and DAM in edtech
What do you like best about the product?
I like that it is relatively user friendly and granular which makes content re-use easier.
What do you dislike about the product?
I dislike that there are not very many comprehensive administrative reporting tools. I also struggle with Brightspot being a marketing CMS that does not always work for our use cases in education.
What problems is the product solving and how is that benefiting you?
Brightspot is helping us work to streamline our workflows and encourages content re-use to improve consistency and efficiency.
Incredibly flexible CMS with tons of use cases
What do you like best about the product?
I like Brightspot’s unique ability to handle content across multiple websites. As a local publication serving 30+ cities across the United States, it’s important for our users to collaborate and share content across our various sites. Brightspot makes standardization, content sharing, and third party integrations a breeze.
What do you dislike about the product?
If a feature that you’re looking for is not “out-of-the box”, Brightspot can get quite costly as a platform. I recommend hiring in-house front end and backend developers if you plan to move forward with the Brightspot CMS platform.
What problems is the product solving and how is that benefiting you?
Our team is able to write and publish articles, then populate and adjust the content to fit our newsletter format. We’re also able to publish and schedule our newsletters without ever leaving the CMS.
Customizable and innovative
What do you like best about the product?
I love that bright spot is customizable for each organization.
What do you dislike about the product?
The design has a more old-school vibe, reminiscent of the early Mac processors.
What problems is the product solving and how is that benefiting you?
Unifying our global branding and customizable for each level of user
Great presentations!!
What do you like best about the product?
The GEO presentation was great. Many of the topics were new to me, which made it very enriching to learn about the latest developments happening on the AI side.
What do you dislike about the product?
I actually didn't see anything that I dislike.
What problems is the product solving and how is that benefiting you?
We are not using brighspot yet, we are actually studing it as a possibility, but it seems to be very usefull
Brightspot is great
What do you like best about the product?
Brightspot has given us a flexible option to host all of our microsites. It is easy to use and constantly improving. Our contacts at Brightspot are wonderful!
What do you dislike about the product?
We have struggled in the past with up-time and unannounced maintenance windows, but that has mostly been resolved.
What problems is the product solving and how is that benefiting you?
We have a scalable, flexible, secure solution for hosting our microsites
showing 11 - 20