4 ms·

How would a privacy first SaaS with a localhost option work from both business and technical perspectives?

• jvanderbot 3y ago
  Access to fine-grained, well-classified financial data costs money. The localhost option provides a way for you to integrate with providers of said data, e.g., using their "developer" api keys. As long as they support free personal use and you stay in their limits, the localhost option incurs no cost to you, and we have no reason (and no way!) to charge anything if you `git pull` and set up these integrations using our readme.md. All storage will be encrypted w/ client side keys. For SaaS, we do the integration automatically and pass hosting and fintech costs on as a monthly subscription. We provide automatic report options that also incur small charges, mostly to cover additional compute, hosting, and higher-tier integration with data providers. These reports can use transient data and/or pass encrypted payloads to client side report generation or display, e.g., SPA or CLI tools.
  • wewtyflakes 3y ago
    Would it be possible to use the SaaS offering for a bit, then transition to the local option, and vice-versa, without losing my data?
    • jvanderbot 3y ago
      That's a good idea, I don't immediately see technical problems. It wasn't on the roadmap but we'll add it.
  • j45 3y ago
    Well answered how it's possible. :) If there is a link to sign up for a mailing list I'd be happy to be notified