Company

SLAtech: the developers who built SLAtech Vantage for their own work

An Israeli software development and AI company since 2004. What we build, how we treat your code, and what you can check.

SLAtech Vantage is built by SLAtech LTD, an Israeli software development and AI company founded in 2004. We built it for our own development work for a client, and we work in it ourselves. This page is for developers and CTOs: how we treat your code and data, how we test and release changes, and which tools it connects to. Only what can be checked.

Who we are

SLAtech LTD is an Israeli company that develops software and works with artificial intelligence. It was founded in 2004 and builds enterprise systems that people work in every day, with AI inside them rather than next to them.

SLAtech Vantage is our product. We develop it, run it and support it.

Built by developers, for their own work

SLAtech Vantage did not start as a product idea. It grew out of a long-running development project we carry out for a client: tasks arrived from the client's ticket system, hours were kept in spreadsheets, decisions sat in mail, and the monthly report was assembled by hand. We built the tool so that all of this is collected from where the work already happens, and we work in it ourselves on that project.

That is why the product is shaped around the problems a development team actually has, not around a list of features.

How we treat your code and data

  • The repository is only read. The GitHub connection pulls commits and failed GitHub Actions runs, and SLAtech Vantage writes nothing to your repository. Jira and the error trackers are connected read-only as well.
  • Personal identifiers are hidden before the language model. Before work text is sent to the model, email addresses, Israeli phone and ID numbers, passwords and keys written in the text, and names the system knows are replaced with labels. The real values stay with us, encrypted. Masking relies on patterns and a dictionary, so a name the system does not know can get through, and specification documents uploaded for an hours estimate are sent to the model as they are.
  • Clients are separated by organization and project. A person's access is derived from their organization's participation in a project, and a filter on every query limits the data to those projects.
  • Keys are encrypted and never shown again. A Jira, GitHub or other token is encrypted before it is stored, and once saved it is not shown in the interface and not written to server logs.

Each mechanism, limits included, is described on the security and privacy page.

How we build it

  • Automated tests. The code is covered by more than 9,700 automated tests, and they pass before a change goes out.
  • A check after every release. Every release ends with an automatic check of the live service, and a release whose service does not report healthy counts as failed. After that we check the live site itself: a green build only says the files were copied.
  • A public changelog. What changed each month is written in the changelog.

We write here only what we can show. This page makes no claim of ISO, SOC or any other certification.

Works with the tools you already use

Your team does not have to move to a new tool. SLAtech Vantage connects to where the work already happens:

  • Tasks: Jira, Azure DevOps, Freshservice, Trello, Asana, ClickUp, monday.com, Linear.
  • Code: GitHub, GitLab, Bitbucket, and failed runs in GitHub Actions and GitLab CI.
  • Errors: Sentry, Rollbar, Bugsnag, Application Insights. There is no agent to install and no library to add to the code.
  • Hours: Toggl Track, Clockify, Harvest, Everhour, TimeCamp.
  • Mail and conversations: Gmail, and WhatsApp chats loaded as an export file.

More on the connections: Jira, GitHub, error trackers, time trackers.

Good to know before you start

  • The interface is available in Hebrew, English and Russian. Every user has their own language setting: Hebrew is shown right to left, English and Russian left to right, and the client portal follows the same setting. Outgoing messages are sent in the recipient's language.
  • You can start with a 14-day trial, no credit card required. Current prices are on the pricing page.

This page has no client list and no awards, only facts that can be checked.

Frequently asked questions

Who develops SLAtech Vantage?
SLAtech Vantage is developed, run and supported by SLAtech LTD, an Israeli software development and AI company. The product grew out of a long-running development project the company carries out for a client, and its team works in it on that project: the project's tasks, hours, correspondence and errors are collected in SLAtech Vantage.
Since when has SLAtech been operating?
SLAtech LTD was founded in Israel in 2004. Since then it has developed software, mostly enterprise systems, and brought artificial intelligence into them. SLAtech Vantage is the company's product: a client portal for software projects that brings tasks, time entries, correspondence, code activity and monitoring into one place.
Do we need to install an agent or a library in our code?
No. SLAtech Vantage connects to the tools you already use through their APIs, with an access token or an ordinary sign-in consent: Jira, GitHub, GitLab, error trackers, time trackers and Gmail. It reads errors from Sentry, Rollbar, Bugsnag or Application Insights, and from failed GitHub Actions runs and GitLab CI pipelines, without an agent and without a library in the code. The GitHub and Jira connections are read-only.
Is our client's data sent to an AI model?
Some work text is, and only after masking. Before text is sent to the language model, email addresses, Israeli phone and ID numbers, passwords and keys written in the text, and names the system knows are replaced with labels. The real values stay with us, encrypted, and are put back into the answer only from the map of that same request. Masking relies on patterns and a dictionary, so an unknown name can get through. Specification documents uploaded for an hours estimate are sent without masking.
Which languages does SLAtech Vantage work in?
Hebrew, English and Russian. Every user has their own language setting, and the interface, including the client portal, is shown in it: Hebrew right to left, English and Russian left to right. Outgoing messages such as a project invitation or an error alert are also sent in the recipient's language. You can contact SLAtech in any of the three languages.

Want to see how SLAtech Vantage looks on your own project? You can start with a trial, no card required.

Start a free trial