3 ms·

Congrats on launching! > a backend API for app/component definitions hosted by us to simplify pushing feature updates Any plans to open-source that part as we

• ayazhan 3y ago
  frankly we're new to open source. and technically we're not really open source. we wanted to take advantage of the self hosted nature of data processing worker, which are safety, extensibility, and developer trust. that's why the worker is under the source-available model. as we grow and learn, if we get interest from the community to contribute, we'll definitely consider opening more of the codebase.
  • jimmyechan 3y ago
    Also fun fact: originally we only intended to enable self-hosting for the Worker, but we ended up enabling self-hosting for the Client too. If we also end up enabling self-hosting for our backend API then we'd probably rethink our distribution approach