The new languages are Java, Kotlin, Scala, C/C++, Objective C, C#, Go, Typescript, HTML/CSS and Less. Kite works in most popular development environments, including the likes of VS Code, JupyterLab, Vim, Sublime and Atom, as well as all Jetbrains IntelliJ-based IDEs, including Android Studio.
This will make Kite a far more attractive solution for a lot of developers. Currently, the company says, it saves its most active developers from writing about 175 “words” of code every day. One thing that always made Kite stand out is that it ranks its suggestions by relevance — not alphabetically as some of its non-AI driven competitors do. To build its models, Kite fed its algorithms code from GitHub .
The service is available as a free download for Windows users and as a server-powered paid enterprise version with a larger deep learning model that consequently offers more AI smarts, as well as the ability to create custom models. The paid version also includes support for multi-line code completion, while the free version only supports line-of-code completions.
Kite notes that in addition to adding new languages, Kite also spent the last year focusing on the user experience, which should now be less distracting and, of course, offer more relevant completions.
Layer is not trying to replace Excel or Google Sheets. Instead the Berlin-based productivity startup wants to make life easier for those whose job entails wrangling massive spreadsheets and managing data inputs from across an organization — such as for budgeting, financial reporting or HR functions — by adding a granular control access layer on top.
The idea for a ‘SaaS to supercharge spreadsheets’ came to the co-founders as a result of their own experience of workflow process pain-points at the place they used to work, as is often the case with productivity startups.
“Constantin [Schünemann] and I met at Helpling, the marketplace for cleaning services, where I was the company’s CFO and I had to deal with spreadsheets on a daily level,” explains co-founder Moritz ten Eikelder. “There was one particular reference case for what we’re building here — the update of the company’s financial model and business case which was a 20MB Excel file with 30 different tabs, hundreds of roles of assumptions. It was a key steering tool for management and founders. It was also the basis for the financial reporting.
“On average it needed to be updated twice per month. And that required input by around about 20-25 people across the organization. So right then about 40 different country managers and various department heads. The problem was we could not share the entire file with [all the] people involved because it contained a lot of very sensitive information like salary data, cash burn, cash management etc.”
While sharing a Dropbox link to the file with the necessary individuals so they could update the sheet with their respective contributions would have risked breaking the master file. So instead he says they created individual templates and “carve outs” for different contributors. But this was still far from optimal from a productivity point of view. Hence feeling the workflow burn — and their own entrepreneurial itch.
“Once all the input was collected from the stakeholders you would start a very extensive and tedious copy paste exercise — where you would copy from these 25 difference sources and insert them data into your master file in order to create an up to date version,” says ten Eikelder, adding: “The pain points are pretty clear. It’s an extremely time consuming and tedious process… And it’s extremely prone to error.”
Enter Layer: A web app that’s billed as a productivity platform for spreadsheets which augments rather than replaces them — sitting atop Microsoft Excel and Google Sheets files and bringing in a range of granular controls.
The idea is to offer a one-stop shop for managing access and data flows around multi-stakeholder spreadsheets, enabling access down to individual cell level and aiding collaboration and overall productivity around these key documents by streamlining the process of making and receiving data input requests.
“You start off by uploading an Excel file to our web application. In that web app you can start to build workflows across a feature spectrum,” says Schünemann — noting, for example, that the web viewer allows users to drag the curser to highlight a range of cells they wish to share.
“You can do granular user provisioning on top of that where in the offline world you’d have to create manual carve outs or manual copies of that file to be able to shield away data for example,” he goes on. “On top of that you can then request input [via an email asking for a data submission].
“Your colleagues keep on working in their known environments and then once he has submitted input we’ve built something that is very similar to a track changes functionality in Word. So you as a master user could review all changes in the Layer app — regardless of whether they’re coming through Excel or Google Sheets… And then we’ve built a consolidation feature so that you don’t need to manually copy-paste from different spreadsheets into one. So with just a couple of clicks you can accept changes and they will be taken over into your master file.”
Layer’s initial sales focus is on the financial reporting function but the co-founders say they see this as a way of getting a toe in the door of their target mid-sized companies.
The team believes there are wider use-cases for the tool, given the ubiquity of spreadsheets as a business tool. Although, for now, their target users are organizations with between 150-250 employees so they’re not (yet) going after the enterprise market.
“We believe this is a pretty big [opportunity],” Schünemann tells TechCrunch. “Why because back in 2018 when we did our first research we initially started out with this one spreadsheet at Helpling but after talking to 50 executives, most of them from the finance world or from the financial function of different sized companies, it’s pretty clear that the spreadsheet dependency is still to this day extremely high. And that holds true for financial use cases — 87% of all budgeting globally is still done via spreadsheets and not big ERP systems… but it also goes beyond that. If you think about it spreadsheets are really the number one workflow platform still used to this day. It’s probably the most used user interface in any given company of a certain size.”
“Our current users we have, for example, a real estate company whereby the finance function is using Layer but also the project controller and also some parts of the HR team,” he adds. “And this is a similar pattern. You have similarly structured workflows on top of spreadsheets in almost all functions of a company. And the bigger you get, the more of them you have.
“We use the finance function as our wedge into a company — just because it’s where our domain experience lies. You also usually have a couple of selective use cases which tend to have these problems more because of the intersections between other departments… However sharing or collecting data in spreadsheets is used not only in finance functions.”
The 2019 founded startup’s productivity platform remains in private beta for now — and likely the rest of this year — but they’ve just nabbed €5 million (~$5.6M) in seed funding to get the product to market, with a launch pegged for Q1 2021.
The seed round is led by Index Ventures (Max Rimpel is lead there), and with participation from earlier backers btov Partners. Angel investors also joining the seed include Ajay Vashee (CFO at Dropbox); Carlos Gonzales-Cadenaz (COO of GoCardless), Felix Jahn (founder and CEO of McMakler), Matt Robinson (founder of GoCardless and Nested) and Max Tayenthal (co-founder and CFO of N26).
Commenting in a statement, Index’s Rimpel emphasized the utility the tool offers for “large distributed organizations”, saying: “Spreadsheets are one of the most successful UI’s ever created, but they’ve been built primarily for a single user, not for large distributed organisations with many teams and departments inputting data to a single document. Just as GitHub has helped developers contribute seamlessly to a single code base, Layer is now bringing sophisticated collaboration tools to the one billion spreadsheet users across the globe.”
On the competition front, Layer said it sees its product as complementary to tech giants Google and Microsoft, given the platform plugs directly into those spreadsheet standards. Whereas other productivity startups, such as the likes of Airtable (a database tool for non-coders) and Smartsheets (which bills itself as a “collaboration platform”) are taking a more direct swing at the giants by gunning to assimilate the spreadsheet function itself, at least for certain use cases.
“We never want to be a new Excel and we’re also not aiming to be a new Google Sheets,” says Schünemann, discussing the differences between Layer and Airtable et al. “What Github is to code we want to be to spreadsheets.”
Given it’s working with the prevailing spreadsheet standard it’s a productivity play which, should it prove successful, could see tech giants copying or cloning some of its features. Given enough scale, the startup could even end up as an acquisition target for a larger productivity focused giant wanting to enhance its own product offering. Though the team claims not to have entertained anything but the most passing thoughts of such an exit at this early stage of their business building journey.
“Right now we are really complementary to both big platforms [Google and Microsoft],” says Schünemann. “However it would be naive for us to think that one or the other feature that we build won’t make it onto the product roadmap of either Microsoft or Google. However our value proposition goes beyond just a single feature. So we really view ourselves as being complementary now and also in the future. Because we don’t push out Excel or Google Sheets from an organization. We augment both.”
“Our biggest competitor right now is probably the ‘we’ve always done it like that’ attitude in companies,” he adds, rolling out the standard early stage startup response when asked to name major obstacles. “Because any company has hacked their processes and tools to make it work for them. Some have built little macros. Some are using Jira or Atlassian tools for their project management. Some have hired people to manage their spreadsheet ensembles for them.”
On the acquisition point, Schünemann also has this to say: “A pre-requisite for any successful exit is building a successful company beforehand and I think we believe we are in a space where there are a couple of interesting exit routes to be taken. And Microsoft and Google are obviously candidates where there would be a very obvious fit but the list goes beyond that — all the file hosting tools like Dropbox or the big CRM tools, Salesforce, could also be interesting for them because it very much integrates into the heart of any organization… But we haven’t gone beyond that simple high level thought of who could acquire us at some point.”
Michael Fraser is an Air Force Veteran and co-founder of Refactr, a DevSecOps automation platform that helps tech teams modernize towards IT-as-code.
Conduct an online search and you’ll find close to one million websites offering their own definition of DevSecOps.
Why is it that domain experts and practitioners alike continue to iterate on analogous definitions? Likely, it’s because they’re all correct. DevSecOps is a union between culture, practice and tools providing continuous delivery to the end user. It’s an attitude; a commitment to baking security into the engineering process. It’s a practice; one that prioritizes processes that deliver functionality and speed without sacrificing security or test rigor. Finally, it’s a combination of automation tools; correctly pieced together, they increase business agility.
The goal of DevSecOps is to reach a future state where software defines everything. To get to this state, businesses must realize the DevSecOps mindset across every tech team, implement work processes that encourage cross-organizational collaboration, and leverage automation tools, such as for infrastructure, configuration management and security. To make the process repeatable and scalable, businesses must plug their solution into CI/CD pipelines, which remove manual errors, standardize deployments and accelerate product iterations. Completing this process, everything becomes code. I refer to this destination as “IT-as-code.”
Why is DevSecOps important?
Whichever way you cut it, DevSecOps, as a culture, practice or combination of tools, is of increasing importance. Particularly these days, with more consumers and businesses leaning on digital, enterprises find themselves in the irrefutable position of delivering with speed and scale. Digital transformation that would’ve taken years, or at the very least would’ve undergone a period of premeditation, is now urgent and compressed into a matter of months.
The keys to a successful DevSecOps program
Security and operations are a part of this new shift to IT, not just software delivery: A DevSecOps program succeeds when everyone, from security, to operations, to development, is not only part of the technical team but able to share information for repeatable use. Security, often seen as a blocker, will uphold the “secure by design” principle by automating security code testing and reviews, and educating engineers on secure design best practices. Operations, typically reactive to development, can troubleshoot incongruent merges between engineering and production proactively. However, currently, businesses are only familiar with utilizing automation for software delivery. They don’t know what automation means for security or operations. Figuring out how to apply the same methodology throughout the whole program and therefore the whole business is critical for success.
Security and encryption experts from around the world are joining a number of organizations to call on India to reconsider its proposed amendments to local intermediary liability rules.
In an open letter to India’s IT Minister Ravi Shankar Prasad on Thursday, 27 security and cryptography experts warned the Indian government that if it goes ahead with its originally proposed changes to the law, it could weaken security and limit the use of strong encryption on the internet.
The Indian government proposed (PDF) a series of changes to its intermediary liability rules in late December 2018 that, if enforced, would require millions of services operated by anyone from small and medium businesses to large corporate giants such as Facebook and Google to make significant changes.
The originally proposed rules say that intermediaries — which the government defines as those services that facilitate communication between two or more users and have five million or more users in India — will have to proactively monitor and filter their users’ content and be able to trace the originator of questionable content to avoid assuming full liability for their users’ actions.
“By tying intermediaries’ protection from liability to their ability to monitor communications being sent across their platforms or systems, the amendments would limit the use of end-to-end encryption and encourage others to weaken existing security measures,” the experts wrote in the letter, coordinated by the Internet Society .
With end-to-end encryption, there is no way for the service provider to access its users’ decrypted content, they said. Some of these experts include individuals who work at Google, Twitter, Access Now, Tor Project and World Wide Web Consortium.
“This means that services using end-to-end encryption cannot provide the level of monitoring required in the proposed amendments. Whether it’s through putting a ‘backdoor’ in an encryption protocol, storing cryptographic keys in escrow, adding silent users to group messages, or some other method, there is no way to create ‘exceptional access’ for some without weakening the security of the system for all,” they added.
Technology giants have so far enjoyed what is known as “safe harbor” laws. The laws, currently applicable in the U.S. under the Communications Decency Act and India under its 2000 Information Technology Act, say that tech platforms won’t be held liable for the things their users share on the platform.
Many organizations have expressed in recent days their reservations about the proposed changes to the law. Earlier this week, Mozilla, GitHub and Cloudflare requested the Indian government to be transparent about the proposals that they have made to the intermediary liability rules. Nobody outside the Indian government has seen the current draft of the proposal, which it plans to submit to India’s Supreme Court for approval by January 15.
Among the concerns raised by some is the vague definition of “intermediary” itself. Critics say the last publicly known version of the draft had an extremely broad definition of the term “intermediary,” that would be applicable to a wide-range of service providers, including popular instant messaging clients, internet service providers, cyber cafes and even Wikipedia.
A senior executive with an American technology company, who requested anonymity, told TechCrunch on Wednesday that even as the proposed changes to the intermediary guidelines need major changes, it is high time that the Indian government decided to look into this at all.
“Action on social media platforms, and instant communications services is causing damage in the real world. Spread of hoax has cost us more than at least 30 lives. If tomorrow, someone’s sensitive photos and messages leak on the internet, there is currently little they can expect from their service providers. We need a law to deal with the modern internet’s challenges,” he said.