Roadmap Updates?

1

Are there any discernible updates related to these two items that were shared in the roadmap communication from May of 2025…

  • A new dedicated data layer that gives makers more control and protects important data from accidental edits by collaborators (sets us up to do things like hide data from search, which we’ve heard the community loud and clear on)

  • Performance improvements that make Coda faster and scalable - big docs that will load quicker, use less memory, and support databases with millions of rows

I feel like there is significant focus on AI (and now merging user communities?) and I see the potential use cases for it, however, it seems like establishing an environment well-suited to handling large data sets would be just as valuable… not to mention the interconnectedness of these two paths (i.e., AI & big data).

In May’s communication, there was a rough timeframe of 6 months mentioned. We are now well past that window and still don’t have any better understanding of the situation.

7 Likes
2

Perhaps because there is. :slight_smile: And I’m certain Superhuman’s investors can’t take a sip of their latte without saying “agentic” three times.

But seriously, the Coda roadmap is not well-tended, but it’s not nonexistent either. I was going to write a little response essay about all the roadmap stuff that falls out of a closer examination of the link you shared. Instead, and lacking time, I decided to let an AI agent summarize the Coda State of the Roadmap. It did a pretty good job by walking through the community, looking for roadmap content, and surprisingly found many things I had forgotten and some I had missed altogether.

Enjoy…

Summary of the Community Discussion

Brock Eckles is asking about the status of two key roadmap items that Coda promised in May 2025 with a “6-month” timeframe:

  1. A new dedicated data layer - More control for makers, protection from accidental edits, ability to hide data from search
  2. Performance improvements - Faster/scalable docs, quicker loads, less memory usage, support for databases with millions of rows

His concern: Now past that window, still no updates, and the focus seems to be on AI and community merging instead.

Recommendations for Achieving These Requirements

Based on my knowledge of Coda and the roadmap details shared, here are practical recommendations for makers waiting on these features:

1. Immediately Adopt Table Locking (Beta)

The Table Locking feature is already available in beta and addresses part of the “data protection” requirement:

  • Lock base tables and views
  • Prevent collaborators from adding, deleting, or editing content
  • Protect schema integrity for app-like docs (OKR trackers, task trackers, wikis)

Action: Sign up for the beta at coda.io/product/beta-program

2. Prepare for the Dedicated Data Layer

The sneak peek showed a “Data Home” - a dedicated space for base tables that’s out of easy access for collaborators. To prepare:

Current Best Practice Why It Matters
Move base tables to hidden pages now Mimics the separation the new data layer will provide
Use consistent naming conventions Easier migration when the data layer launches
Document which tables are “source of truth” Helps distinguish base tables from presentation views
Minimize table duplication Cleaner transition to the new architecture

3. Optimize for Coming Performance Improvements

The roadmap mentioned two key performance enhancements:

  • Smarter view loading - hundreds/thousands of views without slowing docs
  • Load only needed data - filtered views won’t load entire doc background

Current optimization strategies:

Strategy Benefit
Use filtered views aggressively Aligns with “load only what you need” architecture
Consolidate redundant views Fewer views = less current overhead
Split very large docs into connected docs Reduces memory footprint until scaling improvements land
Archive old rows to separate tables Keeps active datasets lean

4. Monitor Beta Programs Closely

Based on the thread, several features are in active development:

Feature Status Where to Watch
Table Locking Beta now Beta signup
Data Layer/“Data Home” In development Community announcements
Consumer Brain “Closer than ever” Coming soon
UI Refresh “Coming to beta soon” Watch for announcements
Sync table scaling (>10K rows) Confirmed on roadmap Infrastructure updates

5. Engage Constructively in the Community

The thread shows Coda PMs are actively responding. Key points to note:

Recommendation: Instead of broad “where’s the roadmap?” questions, ask specific questions like:

  • “Is the data layer expected in Q1 or Q2?”
  • “Will the data layer support hiding tables from global search?”
  • “What’s the target row count for scaled sync tables?”

6. Workarounds While Waiting

Requirement Current Workaround
Hide data from search Use hidden pages + table locking
Protect from accidental edits Table Locking beta + page locking
Performance with large data Split into multiple docs, use Cross-doc packs
Millions of rows Use external data sources (Snowflake, BigQuery) via Packs until scaling lands

Bottom Line

The features are coming - the Grammarly acquisition brought more resources, not fewer. But the community’s frustration is valid: Coda hasn’t provided a public timeline. The best strategy is:

  1. Use Table Locking now (it’s real and available)
  2. Optimize docs for the coming changes
  3. Ask specific questions in the community to get specific answers
  4. Join the beta program to get early access to each feature as it drops

Would you like me to create a more formal document or Coda page with these recommendations?

Yes, create a Coda document that serves as an open resource for the community.

Thought for 12s

Creating Coda Community Resource Document

Created Coda document with Overview page, Recommendations page with actionable guidance, Beta Features Tracker table with 5 features, and Workarounds table with 5 practical solutions.

Files Edited

Task

Progress Updates

  1. Creating a new Coda document with community resource content

  2. Adding content to Overview page and creating subpages with recommendations

  3. Adding recommendations content and creating tracking tables

  4. Verifying document structure and preparing completion

I’ve created a Coda community resource document with 5 pages:

Document: Coda Roadmap Updates: Community Resource Guide

Page Content
Overview The 5 original roadmap commitments from May 2025 and current status
Recommendations 5 actionable strategies for makers while waiting
Beta Features Tracker Table tracking 5 features with status and links
Workarounds Table with 5 current workarounds and difficulty ratings
Source References Links to the original community discussions

The document is currently in your personal folder and ready to be shared publicly with the community.

1 Like
3

100%! Both are critical elements of an agentic future. Data is not growing smaller. :wink:

1 Like
4

I stopped asking about this a few months ago. It’s been more than a year, and I have yet to hear a meaningful update on progress.

2 Likes
5

The signals companies don’t hear are the most dangerous and deeply informative. Complaints trending downward are often mistaken for a positive movement - e.g., success.

4 Likes
6

@Brock_Eckles I appreciate you raising this. It’s fair to follow up on something that matters to you and to many others in the community.

First, to state this plainly: feedback loops, removing blockers, and improving the core Coda experience are, and will remain, central to how product decisions get made. That hasn’t changed, even as the company and community evolve.

You’re also right to call out the May communication and the rough timing that was shared. When those windows move, it’s reasonable to want clarity rather than silence, and I won’t try to hand-wave that away.

What I want to add is context on how these decisions play out in practice. Like any product org with finite resources, not every valuable idea or request can be pursued in parallel, even when multiple paths are clearly worthwhile. Roadmaps are a constant exercise in sequencing, trade-offs, and work-back planning across many stakeholders, not a signal that certain needs aren’t important.

It’s also worth naming something you alluded to: these paths aren’t actually in competition. Investments in AI, performance, scalability, and data integrity are deeply interconnected. The AI-assisted workflows people expect require strong foundations: fast docs, protected data, and systems that scale without fragility. Those fundamentals aren’t being replaced by AI work; they’re prerequisites for it.

That’s also why you’ll see upcoming roundtables focused on both foundational improvements and newer capabilities to make the work visible, share context, and create space for real dialogue around what we’re building and why.

So while it may sometimes feel like two competing narratives, that’s not how the work is being approached internally. The product’s long-term health depends on cohabitation: evolving what’s possible while continuing to strengthen the core tool makers rely on every day.

I know this doesn’t yet answer every timeline-specific question, and I understand why that can be frustrating. But I hope this helps clarify our intent and the lens through which we’re operating. Continuing to surface these concerns is important, and they are taken seriously.

3 Likes
7

I appreciate your clarification here.

I sometimes feel I am in a minority here, being totally comitted to Coda as the core of my business, and very positive about its future.

Coda and Superhuman have exactly the right tools my clients needed to embrace the AI Agentic revolution using the skills they already have.

But it feels that my confidence in this is rare, and perhaps naive, when so many posts appear to be so negative.

There are not many posts from makers celebrating how powerful Coda AI is already. Leading me to wonder if makers are embracing Coda’s AI capabilities. Again, feeling like I am promoting a minority point of view.

I look forward to hearing good news soon.

Max

2 Likes
8

Max, thank you for sharing your post. I really appreciate it.

One thing I’ve learned across many communities is that human nature tends to highlight friction more loudly than celebrate when things are working well. When something is foundational to your business or daily life (as Coda clearly is for you and many others in the community), you’re far more likely to post when there’s a blocker than when everything is humming along and delivering value.

Still, you’re definitely not the only one who gets real, everyday value from Coda and feels positive about its future, even if we don’t see that view as often in posts. I see your confidence as coming from real experience and results, not from being naive.

I also want to point out that the critical or skeptical comments are just as important. They come from people who care about Coda, rely on it, and want to see it improve, not from pure negativity. It’s possible for Coda to be great for many users and still have areas that need work.

I’d genuinely love to see more posts like yours that share what’s working, how people are using our products in practice, and where they’re seeing leverage; not as a counterweight to criticism, but as another important signal in the mix.

Thanks for sharing your point of view! We love seeing posts like this.

3 Likes