Coda, from Coda Project headquartered in San Francisco, is a template-based document generation solution, supporting a variety of use cases presented by the vendor as ideal for smaller companies that might otherwise be relying on spreadsheets to maintain (for instance) product development, or inventory tracking. It is available free, with paid editions to support teams, automations, or for more advanced collaboration and workspace features, as well as more advanced security features.
$0
per month
Statuspage
Score 8.2 out of 10
N/A
Atlassian Statuspage provides status updates for shared cloud resources to users, eliminating duplicate support tickets and displaying uptime status.
$29
per month
Pricing
Coda
Statuspage
Editions & Modules
Free
$0.00
per month
Pro
$10.00
per month per doc maker; unlimited editors (paid annually)
Team
$30.00
per month per doc maker; unlimited editors (paid annually)
Enterprise
Custom Pricing
Hobby
$29
per month
Startup
$99
per month
Business
$399
per month
Enterprise
1,499
per month
Free
Free
Offerings
Pricing Offerings
Coda
Statuspage
Free Trial
Yes
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
Yes
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
With Coda, you only pay for Doc Makers.
Often one person creates a doc, others edit it, and some simply observe from afar. Instead of charging for everyone, we only charge for the people who create docs.
Interested in enterprise pricing? Visit coda.io/enterprise
Coda is great to build a place for your users to go to and see information. It is easy to navigate through and the variety of content creation is great. However, it is not always easy to create what you want and there is a lot of playing around and learning. Coda also sometimes misses some functionality which is expected. For example, downloading a list of users that have access to the platform. Being able to send push notifications when a new page has been created etc. Overall it is a good tool to use just be prepared to invest time!
StatusPage is well suited for notifications on services and products. If you need to have a passive way to notify users, internal staff, or executives on the status of SaaS services, StatusPage is a low barrier way to do this with minimal setup and maintenance. StatusPage is not well suited for scenarios in which you want info kept private. If StatusPage is updated, the subscribers to those alerts will be notified so you just want to make sure you're addressing the right audience with updates.
It takes getting used to in terms of how the formulas per column is implemented, in contrast to how we build tables in Excel. For organization/team purchase, it would be worth considering having a training for the core team of users. Right now, we do a lot of self-learning.
Inability to email charts or image without these objects being hosted on a third party. The community has been great in providing workarounds but it would be much more convenient to be able to have such ability natively.
APAC Support. I'm based in Malaysia, due to timezone differences, even with a livechat implemented, the support for each step and conversation takes up to 24 hours per response. Having some hours covered in our timezone would greatly improve customer support experience.
Coda is definitely something that has been proven to drive positive impact in our organization. We have many divisions that can benefit from this that we have yet to explore. It would definitely be worth renewing.
Coda can seem either really useful or really useless. The extremes of both ends is driven by what our own understanding of what we want to implement. If we lack this understanding, it will be easy to misunderstand Coda's usability especially in the wrong context.
We haven't done any integrations - the initial part of our experience we found that for docs with complex formulas, the page tends to load slowly but in recent months, Coda has improved and optimized the loading times in general and we generally don't find any problems in terms of speed anymore.
Mainly due to timezone differences. I think Coda's support in general is well implemented and executed. They know their stuff and are helpful. But since I'm not in the same timezone, solution rates are slower for me, and that's not something I prefer. I work in customer service, too, and more often than not, time is important. Shortening the solution time would be a much greater experience.
Support is very responsive although we haven't had to contact them in a time of emergency, all of our support inquiries were answered in a timely manner and usually resolved with their first response. Support responsiveness played a big role in our decision since if we need help during downtime, we can't really afford to wait.
I'm relatively inexperienced but this experience is meaningful. It would have been nice to have some guidance from Coda so that we understood more on Coda's purpose and potential.
While all of the products listed have great features and platforms, there was always one thing missing from them that I would need to get from another application. Coda was the first one we used that really combined some of the best parts of those products and allowed us to use it in one place. I also appreciate the flexibility of creating your own framework and workflow, unlike in other tools where you have to follow how they capture data and organize projects.
I would say StatusPage on its own is a great service. StatusPage for Hipchat can only be used with that specific chat client. But on its own StatusPage can be integrated with many tools, like Slack, email notifications, text notifications, etc. I don't know of a tool that compares with StatusPage. You could essentially host your own status site with Greed Yellow or Red statuses, but you would be missing out on the robustness of a tool that keeps historical data, uptime, and segregates services based on components.
I think scalability is definitely good here since it's based on number of doc makers. Implementation into each dept becomes simpler. That being said, due to the nature of our work, we find it easier that we have a "super user" and then a team of other doc makers. This would make the doc creation and management more efficient.
