Sketches of homepage changes

[josevalim]

New slogan: Explore code and data workflows with interactive notebooks?

Use cases

• Elixir devs

  • Interactive environment
  • Production diagnostics
  • System documentation

• Data scientists

  • Analyze data
  • Visualize it (charts, tables, maps)
  • Share and deploy (interactive with inputs and controls, collaborative, password protected)

Features

• Secrets

• Data source: databases, urls, and files (open source, no access to your data), versioned with your notebook

• Transform data: drag and drop a file to get started

• Deployments (Docker and Teams)

• Distributed, backends and Fly integration

[josevalim]

We should also talk about being open source and no lock in. The whole notebook format is carefully designed so it is not tied to any platform. Stamping provides security, without the lock in, and deployments should be possible anyway. :)

[financelurker]

Hi, @josevalim - with "open source" you also mean Livebook Teams, right? I'd like to introduce it to the company I'm currently at, but they will definitely refuse to use an online Software-as-a-Service solution...

[josevalim]

Livebook Teams (which is the server component that coordinates deployments within your infrastructure) is not open source at the moment. But Livebook itself, which is where you author notebooks, is open source. If your application has stronger restrictions, keep in mind that:

1. Livebook Teams does not have access to your secrets and credentials. Everything is encrypted locally in your machine before it is sent to our serves.

2. You can also use Livebook to generate Docker images which you then deploy internally, this way your servers do not need to reach to Livebook Teams servers.