niledatabase / niledatabase

Serverless Postgres for modern SaaS

---

Nile

Nile is serverless Postgres built for modern SaaS applications. All B2B SaaS applications and most B2C SaaS are multi-tenant. A tenant is primarily a company, an organization, or a workspace in your product that contains a group of users. A SaaS application provides services to multiple tenants. Tenant is the basic building block of all SaaS applications.

Nile virtualizes tenants/customers/organizations into Postgres to enable native tenant data isolation, performance isolation between tenants, per-tenant backups, and tenant placement on shared or dedicated compute globally for latency or compliance. You can do all this with the experience of a single Postgres! You don’t have to manage multiple databases, build complex permissions for isolation, or write buggy scripts to read specific tenant data from backups. On top of the tenant model, we provide opt-in user management capabilities, customer-specific vector embeddings, and instant tenant admin dashboards. Moreover, Nile's Postgres is built for the cloud, enabling effortless scaling and a true serverless experience.

We are in private beta currently. You can get an invite by signing up at https://www.thenile.dev/

This is a great resource to read more about Nile in 3 minutes https://www.thenile.dev/docs/nile-in-3-minutes

Features

• Built-in tenant virtualization
• Drop-in tenant and user management
• Onboard tenants once and place them globally - any region, edge or infrastructure
• Instant customer dashboards
• Domain and tenant specific AI embeddings
• Effortlessly elastic
• Fully integrated ready to use UI components
• Extensive support for popular Postgres extensions

Documentation

Nile is in private beta. For documentation, you can check out https://www.thenile.dev/docs. You can get an invite by signing up at https://www.thenile.dev/.

Community & Support

• Community Forum.
• Discord.

niledatabase's Issues

Onboarding fail with 404

When starting for the first time the user-journey is great, but it ended for me at least, in a 404 page.

Of course is not a big deal because you can just reload the console and all was correctly created.

circular link in auth guide docs

This is minor. At the bottom of the auth guide for next.js , there is a link called "Query as a User with Next.js" under the "Next Up:" header. Clicking on this just redirects to the exact same guide url (https://www.thenile.dev/docs/user-authentication/email-login/nextjs) - and brings the scroll to the top since the page is re-rendered. This creates a circular navigation experience, and could be misleading for new users.

I'd suggest either removing this link, or updating to a different "next step" guide for querying users, if one exists.

typo - doc path not matching code example path in auth guide docs

Super minor - but figured I'd create an issue anyways so it can be fixed.

It should only be "ui", not "uid" in the path.

the example implementation seems to set the userId and tenantId on a singleton

in the nodejs/react example the nile server is instantiated in the index.ts file (

niledatabase/examples/quickstart/node_react/src/be/app.ts

Line 8 in 4b2c07f

export const nile = Server({

)

and then in the middleware the following properties are set:

niledatabase/examples/quickstart/node_react/src/be/app.ts

Line 37 in 4b2c07f

nile.token = getUserToken(req.cookies);

  nile.token = getUserToken(req.cookies);
  nile.userId = getUserId(req.cookies);

these values are used in other handlers. this looks like it is introducing a race condition where a next request can overwrite the values before the current request is fully handled? wouldn't it be better to pass the userid and token with the requestcontext?