buildship-ai/rowy

★ 6,812TypeScriptAudience · developerComplexity · 3/5Setup · hard

Mindmap

mindmap
  root((rowy))
    What it does
      Spreadsheet for Firestore
      Edit database records
      Trigger workflows
    Field types
      Text numbers dates
      Image and file upload
      JSON and Markdown
    Integrations
      SendGrid email
      Twilio SMS
      Algolia search
      BigQuery analytics
    Access control
      Role-based permissions
      Table-level rules
      Field-level rules

mindmap root((rowy)) What it does Spreadsheet for Firestore Edit database records Trigger workflows Field types Text numbers dates Image and file upload JSON and Markdown Integrations SendGrid email Twilio SMS Algolia search BigQuery analytics Access control Role-based permissions Table-level rules Field-level rules

Click or tap to explore — scroll the page freely

Things people build with this

USE CASE 1

Manage Firestore database records through a familiar spreadsheet grid without writing code or using the Firebase console

USE CASE 2

Build automated email or messaging workflows that trigger when records change, using pre-built blocks for SendGrid, Twilio, or Algolia

USE CASE 3

Set up role-based access so different team members can only view or edit specific columns in a table

USE CASE 4

Write custom JavaScript or TypeScript Cloud Functions directly in the browser using any npm package

Tech stack

TypeScriptReactFirebaseFirestoreGoogle Cloud Functions

Getting it running

Difficulty · hard Time to first run · 1h+

Requires a Google Cloud Platform project with Firebase and Firestore enabled before deploying.

In plain English

Rowy is a browser-based tool that puts a spreadsheet-like interface on top of a Firebase Firestore database. Firebase is Google's cloud platform, and Firestore is its document-based database. Instead of using Firebase's own admin console or writing queries in code, Rowy lets you view, add, edit, delete, sort, filter, import, and export records directly in a familiar grid. Multiple views of the same data collection can be created and different columns can be shown, hidden, resized, frozen, or renamed. Beyond the database interface, Rowy also lets you build automated workflows that trigger when data changes. These run as Google Cloud Functions, which are small code snippets that execute on Google's servers without you managing infrastructure. You can write JavaScript or TypeScript directly in your browser and use any package from the npm registry. Pre-built code blocks connect to external services like SendGrid for email, Algolia for search, Twilio for messaging, and BigQuery for analytics. Fields support over 30 types, including plain text, numbers, dates, checkboxes, dropdowns, image uploads, file uploads, JSON editors, Markdown editors, and rich text. There are also special field types for triggering actions on a row, aggregating values from nested sub-tables, and pulling data from other collections or external HTTP endpoints. Teams can use role-based access controls to limit what different users can view or edit, with permissions set at the table level and the field level. Built-in user management is included. Rowy runs on your own Google Cloud Platform project. A deploy button walks you through setup, and the service operates entirely within your own GCP environment. The company states it does not access or store your data.

Copy-paste prompts

Prompt 1

Set up Rowy on my GCP project and create a table view for a Firestore collection called orders with columns for name, email, and status

Prompt 2

Write a Rowy Cloud Function in TypeScript that sends a SendGrid email when a new document is added to my users Firestore collection

Prompt 3

How do I configure Rowy field-level permissions so only users with the admin role can edit the price column in my products table?

Prompt 4

Create a Rowy action column that calls an external HTTP endpoint when I click a button on a specific row

Open on GitHub → Explain another repo

← buildship-ai on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.