Coda, acquired by Grammarly in early 2025, is a template-based document creation and collaboration solution, supporting a variety of use cases.
$0
per month
zeroheight
Score 8.6 out of 10
N/A
zeroheight helps teams create, manage and maintain their design systems. Using zeroheight, designers, engineers, and product teams can collaborate and build design systems that can be easily shared across teams.
$49
month
Pricing
Coda by Grammarly
zeroheight
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
Starter
$49
month
Enterprise
Custom Pricing
Offerings
Pricing Offerings
Coda by Grammarly
zeroheight
Free Trial
Yes
No
Free/Freemium Version
Yes
Yes
Premium Consulting/Integration Services
Yes
No
Entry-level Setup Fee
No setup fee
Optional
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!
For creating and maintaining a component library, it is a fantastic tool that creates an interface between Developers, UX Engineers and Designers. It is easy to get both general information about a component, but also incredibly detailed information when looking at the component on a pixel-level, where information on paddings, margins, colors, fonts etc. can be easily accessed.
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.
when opening a component image (which opens a new page where the detailed information like paddings and colors are shown), the zoom can only be done by buttons, I'd prefer to be able to use my mouse scroll and for vertical / horizontal scrolling to do ctrl+scroll or ctrl+shift+scroll or something like that
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.
There is a little bit of a learning curve on where to point and click to add in different elements and make edits. But it is still very manageable once you get the hang of it. I do still have some issues with some of my connected pages updating each other when I don't want them to sync. So I'll end up editing one page, and it will make the same edits on another page.
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.
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 have used and still use Sketch and Zeplin too, but they serve other purposes for us. Sketch is used to design the components themselves and they are then exported to Zeroheight where they are showcased and enriched with textual information. Zeplin is used to design application pages, and again the components are exported to Zeplin from Sketch. But Zeroheight is mainly used for the development of the components themselves as well as a documentation for our design guideline in general. It is also used by us for design tokens and patterns, as well as other information on the design guideline, so if someone wants to understand the "why" of a design decision, the explanation can be usually found in Zeroheight too.
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.
increased quality, as less misunderstandings or communication problems occur
increased speed of development, as it is a single source of truth for us. The developer can rely on the information in Zeroheight being correct so that he doesn't have to iterate his code again and again.
