Bewertungen und Rezensionen

Olá Tiago, obrigado pelo feedback detalhado, ajuda muito a entender o que aconteceu. Um pouco de contexto sobre como o OrcaSheets funciona por baixo: o modelo lê principalmente os cabeçalhos e a estrutura da sua planilha, não os dados linha por linha. Quando os cabeçalhos se perdem durante a importação, o modelo perde o contexto principal que usa para construir gráficos e fazer agregações. Algumas coisas que costumam ajudar em arquivos mais complexos: usar a abordagem multi-sheet para fazer cross-referencing entre tabelas separadas, e dar uma dica ao modelo no seu prompt sobre o que cada coluna representa quando o cabeçalho original não for autoexplicativo. Dito isso, somas saindo erradas é algo que queremos investigar diretamente. Gostaríamos muito de marcar uma chamada com você para olhar o arquivo juntos e encontrar uma solução. Envie sua disponibilidade para [email protected] e marcamos um horário que funcione para você.

We’re sorry for the confusion. On Setapp, OrcaSheets is meant to have all features enabled, and the 30-day indicator is part of an auto-refresh login cycle rather than a restricted trial. The Settings screen is available through the gear icon on the right sidebar, though we agree this should be much more obvious. We’d appreciate it if you could share a screenshot of the Settings screen or confirm whether a referral ID is visible there on [email protected], so we can verify your Setapp activation and understand what felt locked or missing.

Hi SK, thank you for the feedback and we hear you. On the emails, we did introduce a product onboarding sequence to help new users discover features they might otherwise miss, like Recipes, and we understand that may have felt unexpected if you weren't anticipating it. That's on us to communicate better upfront. On the UX and onboarding experience, the feedback is fair and actively being worked on. If you'd like to share anything more specific, we're at [email protected] and we're listening.

Thank you for sharing this, Anudeep. This is exactly the kind of use case we were built for. Moving from cybersecurity to health tech means navigating some of the strictest data governance requirements out there, and we're genuinely glad we could remove that friction for you. Keeping your data on your machine shouldn't mean compromising on analytical capability, and it's great to hear that came through. We'll keep making sure OrcaSheets keeps up with wherever your work takes you!

Glad to hear it, Troy! Let us know how it goes.

Hey Brandon, thanks for the honest feedback! We hear you on the documentation front, and we've been working on it. You can check out our onboarding guide here: https://orcasheets.ai/docs/onboarding-guide/ for a quick start. As for the Snowflake connector, we've just shipped a production-ready version along with sample connection configs for most connectors to make testing a breeze. Give it another spin when you get a chance, and if you hit any snags, we're right here. We'd love to change that 'waste of time' to a 'worth my time' 😊

Hi Jan, that's a fair criticism, and thanks for taking the time to write it out rather than just leaving a star rating. Quick clarifying question so we can dig into this properly: were you trying to load a SQL dump with CREATE TABLE / INSERT statements, or a delimiter-separated file that happened to have a .sql extension? If it was a SQL dump, that path is not fully supported yet, which would explain why the import did not go through. The dialog offering .sql.gz variants without loading them is a separate issue we want to address, and we will review the import experience so the supported formats are clearer up front. We would really like another shot at this. If you can write to us at [email protected] with a bit more detail on the file you were trying to load, we can help you get it working and make sure the rest of the trial goes better. Thanks for flagging this.

Thank you for sharing this so clearly, and we’re sorry for the frustration. A couple of things may have caused what you saw. If the chart started at 1907 instead of 1900, it is possible the earliest valid value in that column was being read as 1907 rather than 1900. For the columns not appearing in the chart builder, this usually happens when those fields are interpreted as text or categorical values instead of numeric ones, and the graph builder currently prioritizes numeric columns. We agree this should feel much more straightforward. We’re improving the chart prompting experience so the AI follows the data more accurately, and we’ve also enabled the AI SQL Editor for you so you can correct column types more easily where needed. That should help bring in fields that may currently be excluded from graphing. Thanks again for the honest feedback - the app should make exploration easier, not harder, and this is exactly the kind of issue we want to fix.

We're sorry this was frustrating. OrcaSheets does support scatter plots, but currently they need to be created through the chart selection flow by choosing the scatter plot visualization and then assigning the relevant columns. We agree that something this basic should not feel complicated, and we're actively improving the product so chart creation, including through chat, becomes much more straightforward.

Thank you for coming back to update your review, Perbinder - that means a lot to us. Really glad the resizing is working for you. If anything else comes up, we're always here.

Thank you for this feedback, and we completely hear you. A cluttered interface that limits how much data you can see defeats the whole purpose. We're working on UI configurability, and resizing for sidebars and drawers is something we're looking to implement in the next upcoming updates. We want OrcaSheets to flex to your workflow, not the other way around. We appreciate your patience while we get there, and we're glad the concept is resonating. Updates are coming.

Thank you, Archiee! Glad it's been helpful for your data analysis. We just launched our AI SQL Editor (beta) that lets you describe your analysis in plain English and writes the SQL for you if you want to take things up a notch. It's a premium feature, but we'd love to get it enabled for you to explore. Drop us a note at [email protected] and we'll set you up.

Hallo Marius, vielen Dank für den Hinweis. Wir haben kürzlich ein Update veröffentlicht, das genau dieses Problem beheben sollte. Wir würden Ihnen gerne helfen, das zu lösen. Schreiben Sie uns gerne eine E-Mail an [email protected], dann können wir einen kurzen Call vereinbaren und sicherstellen, dass alles reibungslos funktioniert. Hi Marius, thank you for flagging this. We recently rolled out an update that should have resolved this exact issue. We'd love to help you get this sorted out. Could you drop us an email at [email protected]? We'll jump on a quick call and make sure everything's working smoothly for you.

Starting something new always comes with a little uncertainty, so it genuinely means a lot to hear that we made the transition easy. Big data without a single SQL query is exactly what we set out to build, and we're so glad it's working for you.

Hi Molly, thank you for taking the time to write this and for being direct about it. You've flagged real gaps and we'd rather hear this than not. The padding and the inconsistent sizing across split-screen configurations - these issues are on our radar and actively being worked on for an upcoming release. You're right that they shouldn't require a workaround. The keyboard shortcuts living inside a PDF is genuinely indefensible and we know it. That's changing too. Reviews like yours are exactly what keep us honest about the surface. We hope you'll give us another look when the next release lands.

Fair point, Tay, and we hear you. Resizing is something we're actively working to support in an upcoming update, so you'll have full control over how OrcaSheets fits into your workspace. Appreciate the patience while we get there!

Hi Guillermo, We're truly sorry about this. One of OrcaSheets' core principles is that we run compute on your full dataset locally, not a sampled subset. Unlike most LLM-based tools that work on partial data and risk hallucinating results, we process every single row. So hearing that your 70k-row file was reduced to 6k is deeply concerning to us. We've already reached out to you personally via email because we want to get to the bottom of this. We're treating it as a priority and will do everything we can to make sure your experience with OrcaSheets changes completely. Thank you for flagging this. Feedback like yours is how we get better.