DomOriginal post
Web Developer
Hi Everyone!
I've been digging into appwrite recently again to evaluate if it would be suitable for my SaaS idea. Think freelancers, agencies, but also public "users" for links are communicating on the platform about files and documents. The basic concept is:
- The software is collaborative, so there are public links to documents, but by default only users have access to those, based on RBAC.
- Users should have a workspace, where they can upload files, invite people into and set their own RBAC rules. They should also be able to set files to private in that Space.
- A workspace can contain many projects (not appwrite projects), with files and directories.
- Users can be part of different organizations, so mutlitple teams / workspaces per user are possible.
- Organizations should be as isolated as possible.
- Files (mostly images and videos), can only be in one workspace at a time. They can be either accessed only by users with accounts or can be public, if shared in a public link (with multiple other files). Default is private though.
- I need a very high security standard, as the files are delicate and need to be encrypted on the server side.
- Files need to generate a preview (especially images and videos)
- Files can have a relationship to each other for references
- Billing would be stripe and should be based upon workspace users and storage (S3), but how pricing will be exactly is currently TBD.
My thoughts and questions so far:
- I was thinking of having only a sinlge Appwrite project, with each user being their own team to invite someone else into or working on their own.
- Each team would double as a workspace, but is this enough separation for multi-tenancy?
- How could I create public "share" urls, if the files are still supposed to be private be default?
- Am I absuing the teams system like this?
- If there could be multiple teams inisde a single organization, how could that be done?
Thank you in advance! Ask away if anything is unclear.
Summary
Developers are considering using Appwrite for a collaborative SaaS platform with RBAC, workspaces, high security standards, encryption, file previews, and relations, with a potential billing system. Concerns include workspace separation, public share URLs, and multi-tenancy within organizations. Potential solution: Consider using a single Appwrite project for each user as a team/workspace but explore further customization for multi-tenancy and public/private file-sharing.