Your code.
Your point of view.

With Sprkl Personal Observability, you immediately see the impact of every code change execution, right in your IDE. Code-level traces, errors, hidden API calls, DB queries, memory usage and other unique insights are now revealed.

Join beta >

We leverage OpenTelemetry
to automatically instrument every code change
and analyze it upon execution

We leverage OpenTelemetry
to automatically instrument every code change and analyze it upon execution

It actually saves time spent on logging and APM dashboards, and helps ship faster

Amir Jerbi

Co-founder and CTO, Aqua Security

Make data-driven decisions. Immediately see your code-change hidden dependencies, inefficiencies and potential issues while coding

No more breakpoints or adding logs to figure out what just happened, what works, and what doesn’t. With personal insights you get to see the complete, yet focused, impact of your own code change execution. Each insight is connected to a specific line of code so you can immediately identify the cause.

Complete the picture with code-level tracing – the missing link of tracing

Sprkl leverages Jaeger and adds code-level traces to OpenTelemetry infra traces and only shows traces that are relevant to your code change.

Utilize the full power of
OpenTelemetry for your Jest
tests

Sprkl is the only way to automatically integrate Personal Observability into your Jest tests right in the IDE. Discover which tests failed due to your code change. Get a trace per test with automated logging for all your mockups and assertions with a powerful Jest instrumentation library we’ve implemented.

Cut down the time it takes to research, plan, code, debug, test and iterate so you can ship better code faster

Sprkl links each line of code with its code-level traces and telemetry data so you can effortlessly write optimized, well thought through code.

How it works

Immediate value
in your IDE

Sprkl plays well with

Frequently
asked questions

  • Sprkl is a Personal Observability platform that provides individual developers with telemetry data and actionable insights about their own code changes. We leverage OpenTelemetry to instrument every code change and analyze it upon execution. We then provide immediate feedback, right in the IDE, that includes traces at the code-level, not only at the infrastructure-level (with an embedded Jaeger instance), insights about jest tests, diff coverage, errors, hidden API calls, DB queries, performance bottlenecks, abnormal memory usage and more.

  • No, unless you really want to :). We think it’s TMI and isn’t helpful. We want to help you focus on what matters.

  • Got new feature suggestion or want to comment on existing ones? Connect with us: Here

  • We focus on what you need to see to ship better code faster. Therefore, we focus on what is relevant to your own code change – how it affects and is affected by system components.  For example, your code-level traces, your hidden API calls, DB queries, messages, memory bottlenecks, diff coverage, errors, etc.

  • We currently support VS Code. We’ll support additional editors shortly.  Tell us which editor you use: Here 

  • And what would this involve? We’re currently working in a closed beta mode with a selected group of developers running Sprkl and providing us with feedback. We will widen our beta in the next couple of months. You’re welcome to join our beta: Here

  • Of course. Sprkl can instrument any git recipe you can think of. For example, you can instrument or exclude: uncommitted changes, my commits only; all commits since I left the main branch; all commits in the last six months, etc. Those are configurable.

  • By using Sprkl, you immediately understand how your code performs. You no longer need to spend time manually collecting data and trying to piece it all together. No more sifting through endless logs or traces, adding breakpoints, or switching from one tool to another. Sprkl helps you research, plan, debug, test, and prevent issues, and investigate existing issues faster so you can focus on writing your best possible code. 

  • Yes and will always be free for a single developer. However, we’d appreciate it if you spread the word amongst your fellow devs and communities that you engage in.

  • Once you sign up for the beta on our website, you’ll get a link to schedule a short kick-off call. We’ll show quickly how Sprkl works and will set you up with an account. It’s a 5 min setup; no further configuration is required.

  • Our local development platform does not engage with any external APIs. Everything runs locally on your host machine, and the data is stored on your docker container and is not exposed to anyone. We do ask for your approval to collect statistical data so we can improve and make Sprkl better. We will only collect these stats upon your approval.

  • We support TS, JS over Node.JS operating with the VSCode extension. We are gradually adding support for additional languages. Please tell us what you’d like us to support:Here.

  • TBA soon – we’re working on it.

  • Using sprkl with TypeScript is as easy as using it for native Javascript. Just make sure that you enable sourcemaps when building the code, and that the sourcemaps are available when running sprkl (either as files with the compiled code or inlined).
    Example using esbuild: esbuild –sourcemap …
    Example using tsc (tsconfig.json):

  • Sprkl is a Personal Observability platform that provides individual developers with telemetry data and actionable insights about their own code changes. We leverage OpenTelemetry to instrument every code change and analyze it upon execution. We then provide immediate feedback, right in the IDE, that includes traces at the code-level, not only at the infrastructure-level (with an embedded Jaeger instance), insights about jest tests, diff coverage, errors, hidden API calls, DB queries, performance bottlenecks, abnormal memory usage and more.

  • We leverage OpenTelemetry to automatically instrument every code change and analyze it upon execution.

  • No. It comes out of the box: you don’t need to deal with the hassle of installing it into your IDE.

  • Once you sign up for the beta on our website, you’ll get a link to schedule a short kick-off call. We’ll show quickly how Sprkl works and will set you up with an account. It’s a 5 min setup; no further configuration is required.

  • We focus on what you need to see to ship better code faster. Therefore, we focus on what is relevant to your own code change – how it affects and is affected by system components.  For example, your code-level traces, your hidden API calls, DB queries, messages, memory bottlenecks, diff coverage, errors, etc.

  • No. Our code instrumentation is done locally, in memory, and not added to the source code. Therefore it doesn’t affect staging or production.

  • Our local development platform does not engage with any external APIs. Everything runs locally on your host machine, and the data is stored on your docker container and is not exposed to anyone. We do ask for your approval to collect statistical data so we can improve and make Sprkl better. We will only collect these stats upon your approval.

  • We support TS, JS over Node.JS operating with the VSCode extension. We are gradually adding support for additional languages. Please tell us what you’d like us to support:Here.

  • Of course. Sprkl can instrument any git recipe you can think of. For example, you can instrument or exclude: uncommitted changes, my commits only; all commits since I left the main branch; all commits in the last six months, etc. Those are configurable.

  • Sprkl currently supports Node V.16 or higher. 

  • By using Sprkl, you immediately understand how your code performs. You no longer need to spend time manually collecting data and trying to piece it all together. No more sifting through endless logs or traces, adding breakpoints, or switching from one tool to another. Sprkl helps you research, plan, debug, test, and prevent issues, and investigate existing issues faster so you can focus on writing your best possible code. 

  • No, unless you really want to :). We think it’s TMI and isn’t helpful. We want to help you focus on what matters.

  • We’re working on it. We aim to show you how your code function changes throughout the entire lifecycle.

  • Local performance overhead is very minimal as we instrument your code change alone, rather than the entire codebase. The instrumentation stays local and won’t apply to your files and will not have any effect on staging or production.

  • No. Sprkl doesn’t change your code functionality or files.

  • We don’t change your code’s functionality in any way. Instead, we add an instrumentation layer to your code that only runs on your local machine. We use our intelligent instrumentation engine to leverage OpenTelemetry (a typical, trustworthy open-source project) to apply our instrumentation to your code automatically.

  • We currently support VS Code. We’ll support additional editors shortly.  Tell us which editor you use: Here 

  • TBA soon – we’re working on it.

  • Our local development platform does not engage with any external APIs. Everything runs locally on your host machine, and the data is stored on your docker container and is not exposed to anyone. We do ask for your approval to collect statistical data so we can improve and make Sprkl better. We will only collect these stats upon your approval.

  • No. Sprkl doesn’t change your code functionality or files.

  • We don’t change your code’s functionality in any way. Instead, we add an instrumentation layer to your code that only runs on your local machine. We use our intelligent instrumentation engine to leverage OpenTelemetry (a typical, trustworthy open-source project) to apply our instrumentation to your code automatically.

  • It’s important for us to get personal feedback from our closed beta users so we can fine-tune our product before making it publicly available on the marketplace.

  • No. Our code instrumentation is done locally, in memory, and not added to the source code. Therefore it doesn’t affect staging or production.

  • Our local development platform does not engage with any external APIs. Everything runs locally on your host machine, and the data is stored on your docker container and is not exposed to anyone. We do ask for your approval to collect statistical data so we can improve and make Sprkl better. We will only collect these stats upon your approval.

  • Using sprkl with TypeScript is as easy as using it for native Javascript. Just make sure that you enable sourcemaps when building the code, and that the sourcemaps are available when running sprkl (either as files with the compiled code or inlined).
    Example using esbuild: esbuild –sourcemap …
    Example using tsc (tsconfig.json):

  • Our local development platform does not engage with any external APIs. Everything runs locally on your host machine, and the data is stored on your docker container and is not exposed to anyone. We do ask for your approval to collect statistical data so we can improve and make Sprkl better. We will only collect these stats upon your approval.

  • Sprkl is a Personal Observability platform that provides individual developers with telemetry data and actionable insights about their own code changes. We leverage OpenTelemetry to instrument every code change and analyze it upon execution. We then provide immediate feedback, right in the IDE, that includes traces at the code-level, not only at the infrastructure-level (with an embedded Jaeger instance), insights about jest tests, diff coverage, errors, hidden API calls, DB queries, performance bottlenecks, abnormal memory usage and more.

  • We leverage OpenTelemetry to automatically instrument every code change and analyze it upon execution.

  • Got new feature suggestion or want to comment on existing ones? Connect with us: Here

  • We’re working on it. We aim to show you how your code function changes throughout the entire lifecycle.

  • Local performance overhead is very minimal as we instrument your code change alone, rather than the entire codebase. The instrumentation stays local and won’t apply to your files and will not have any effect on staging or production.

  • No. Sprkl doesn’t change your code functionality or files.

  • We don’t change your code’s functionality in any way. Instead, we add an instrumentation layer to your code that only runs on your local machine. We use our intelligent instrumentation engine to leverage OpenTelemetry (a typical, trustworthy open-source project) to apply our instrumentation to your code automatically.

  • We currently support VS Code. We’ll support additional editors shortly.  Tell us which editor you use: Here 

  • TBA soon – we’re working on it.

  • Sprkl currently supports Node V.16 or higher. 

  • It’s important for us to get personal feedback from our closed beta users so we can fine-tune our product before making it publicly available on the marketplace.

  • By using Sprkl, you immediately understand how your code performs. You no longer need to spend time manually collecting data and trying to piece it all together. No more sifting through endless logs or traces, adding breakpoints, or switching from one tool to another. Sprkl helps you research, plan, debug, test, and prevent issues, and investigate existing issues faster so you can focus on writing your best possible code. 

  • No, unless you really want to :). We think it’s TMI and isn’t helpful. We want to help you focus on what matters.

  • No. It comes out of the box: you don’t need to deal with the hassle of installing it into your IDE.

  • Once you sign up for the beta on our website, you’ll get a link to schedule a short kick-off call. We’ll show quickly how Sprkl works and will set you up with an account. It’s a 5 min setup; no further configuration is required.

  • We focus on what you need to see to ship better code faster. Therefore, we focus on what is relevant to your own code change – how it affects and is affected by system components.  For example, your code-level traces, your hidden API calls, DB queries, messages, memory bottlenecks, diff coverage, errors, etc.

  • No. Our code instrumentation is done locally, in memory, and not added to the source code. Therefore it doesn’t affect staging or production.

  • Our local development platform does not engage with any external APIs. Everything runs locally on your host machine, and the data is stored on your docker container and is not exposed to anyone. We do ask for your approval to collect statistical data so we can improve and make Sprkl better. We will only collect these stats upon your approval.

  • We support TS, JS over Node.JS operating with the VSCode extension. We are gradually adding support for additional languages. Please tell us what you’d like us to support:Here.

  • Of course. Sprkl can instrument any git recipe you can think of. For example, you can instrument or exclude: uncommitted changes, my commits only; all commits since I left the main branch; all commits in the last six months, etc. Those are configurable.

  • We leverage OpenTelemetry to automatically instrument every code change and analyze it upon execution.

  • Local performance overhead is very minimal as we instrument your code change alone, rather than the entire codebase. The instrumentation stays local and won’t apply to your files and will not have any effect on staging or production.

  • No. Our code instrumentation is done locally, in memory, and not added to the source code. Therefore it doesn’t affect staging or production.

  • We’re working on it. We aim to show you how your code function changes throughout the entire lifecycle.

  • No. Sprkl doesn’t change your code functionality or files.

  • We don’t change your code’s functionality in any way. Instead, we add an instrumentation layer to your code that only runs on your local machine. We use our intelligent instrumentation engine to leverage OpenTelemetry (a typical, trustworthy open-source project) to apply our instrumentation to your code automatically.

  • Got new feature suggestion or want to comment on existing ones? Connect with us: Here

  • And what would this involve? We’re currently working in a closed beta mode with a selected group of developers running Sprkl and providing us with feedback. We will widen our beta in the next couple of months. You’re welcome to join our beta: Here

  • Yes and will always be free for a single developer. However, we’d appreciate it if you spread the word amongst your fellow devs and communities that you engage in.

    • Using sprkl with TypeScript is as easy as using it for native Javascript. Just make sure that you enable sourcemaps when building the code, and that the sourcemaps are available when running sprkl (either as files with the compiled code or inlined).
      Example using esbuild: esbuild –sourcemap …
      Example using tsc (tsconfig.json):

    • No, unless you really want to :). We think it’s TMI and isn’t helpful. We want to help you focus on what matters.

    • We’re working on it. We aim to show you how your code function changes throughout the entire lifecycle.

    • Sprkl currently supports Node V.16 or higher. 

    • No. It comes out of the box: you don’t need to deal with the hassle of installing it into your IDE.

    • Once you sign up for the beta on our website, you’ll get a link to schedule a short kick-off call. We’ll show quickly how Sprkl works and will set you up with an account. It’s a 5 min setup; no further configuration is required.