Release notes

New features and changes in Aito

December 20th 2019

We are working through the waitlist of users that have requested access to Aito, still at a rather modest rate as we want to ensure everyone has the best possible experience. We are also still limiting the new instance provision in Console by reviewing the requests. Next couple of weeks of holiday season means things progress a bit slower. Hang in there, your turn will come soon!

Should you have questions or need help, the team is best reached through our public Slack channel.

Soon-to-be-public Aito Console:

  • We realised that we’re too deep into our own work. Some stuff was no longer obvious, so we’ve added some hints and tips on the way, to make it a bit easier to find your way around.
  • We don’t store any passwords. Ever. It’s a promise. We’re using Auth0 for login, which allows you to sign in using your Google account as well as by creating a username/password. It’s, of course, possible to combine those, but that caused an embarrassing bug where you could no longer log in at all after combining the logical accounts. It’s been fixed now.
  • Google logins now also work for non-Aito accounts. The default setting had not been changed, and we didn’t test this with enough different emails.
  • Emails sent by the Console did not actually get sent. This was the case with Auth0-verification emails. We’ve tuned the settings now.
  • The email content is also a bit more human now, as we started thinking more in lines of people than computers.

Aito CLI and integrations:

  • The CLI documentation is getting some TLC as well. It’s on Github, so this will keep on improving all the time.
  • The CLI is getting initial support for SQL-2-Aito. We’re starting off with Mysql and Postgresql, but plan to add support for other databases as well. We’re using ODBC-drivers for this, so it’s mostly a testing bandwidth issue to add more technologies here.


  • With all the stuff going on with the website, we figured we’re having a hard time staying on top of everything ourselves. We started using BugHerd that adds a small “Send feedback” button on the right bottom corner. Please use it and tell us where we’re failing. Please. - We’ll make sure to fix them ASAP. It’s on Console too. On that note, we changed the website to make the structure easier to traverse. Things should be easier to find now.

Bug fixes:

  • We’ve had a long-running stability issue, where massive writing cause environments to start failing health checks. We finally found and squashed the bug! Yeah! The root cause was starvation of the request threads, while all capacity was being used for writing. The change is being rolled out to everyone, everywhere during the normal cycle.
  • Another nasty database bug was the fact that deletions were not complete. Features with zero frequency were never removed. This would’ve been an issue most likely only in our stress testing, but it’s nice to know this won’t happen to you, our dear users.

December 6th 2019

We are getting readier than ever for publicly rolling out the Aito Console, which means our users can manage their teams and API keys as well as see usage stats online. While loads of the work lately has gone to the Console, we were also putting together some educational content and as a result, tadaaa, Aito is now on Youtube! Head over to check the content our amazing Customer Success Engineer Maria has been putting together to help you take the first steps with Aito.

Soon-to-be-public Aito Console:

  • We’ve moved the Terms of Service to the console. This way you can read and accept the terms without physical contract hassle that has been a bit of a burden lately. We’re of course still available for questions, should there be any.
  • You can now request new instances right from the main page, with less clicks. Note, we are for the time being still limiting the creation of new instances, as we want to ensure the best experience and performance to those who already use Aito.

Aito CLI and integrations:

  • We have started collecting still experimental tools under aito-python-tools repository, where we have for example super useful Aito CLI tool that allows you to infer schema and quickly add data to Aito from JSON, CVS and XLS files.

Bug fixes:

  • There was an embarrassing bug where you could try to do a modulo-query on a string field and get rewarded with an Internal Server Error. Ooops! It’s been fixed now, though.
  • We’ve squashed a massive number of bugs in the console. Even before you saw them.

November 22nd 2019

  • We’ve added a new comprehensive example for showing Aito in action: the Kickstarter funding prediction. It’s available online at, live at Slush or in meetings with your favourite Aito people
  • The Aito self-service experience is function-complete. We will be rolling out access to the people in the waiting line soon, and general availability will happen within a few weeks. Stay tuned for more details.
  • We improved the update process, so we can now roll out changes and security fixes much smoother than before
  • We have improved the validation during the schema creation. Unknown analyzers are now reported correctly rather than throwing an exception
  • Representation learning is now one step closer. Basically this will allow Aito to group statistically related features automatically. As a result, the query results will improve and the explanations will get better. In short Aito will become smarter. This is a big improvement, but also a huge change. Thus, we’re rolling out the feature in selected use-cases, and step by step. There will be more details in our blog later.

October 3rd 2019

  • Better support for numeric data
    • With $numeric proposition, Aito can now detect proximity between input values

September 9th 2019

  • Extended language analyzer support:

    • support for many new languages
    • configure stop and key words
  • New text analyzers:

Visit us

Annankatu 34 B

00100 Helsinki


See map

470 Ramona St.

Palo Alto

CA 94301, USA

See map

Contact info

We'd love to hear from you.

Follow us