Everifin is a universal internet banking platform that allows users to connect any bank account within the European Economic Area and see the balances and transaction history under one roof. Everifin can also manage e-invoices, transfer funds between bank accounts and facilitate payments for e-commerce and in the shops. 

The Everifin team was searching for a software development company, which could build a presentational website about their financial services quickly and reliably. The Everifin website should be designed according to the provided web designs in Figma with some animations suggested by the Webscope team to make the entire website more appealing to potential customers. Furthermore, one of the most important features was to provide the website with multiple language mutations because Everifin has clients in many European countries. After discussing the project in detail, we knew that the timeframe for the project would be very challenging for us. 

At Webscope, we dedicated the Everifin project to three developers. We split the job into many minor issues based on individual sections and components in the website. We were focused on delivering the first version in the minimum amount of time while still doing code reviews and keeping the best practices of today. 

We agreed with the client on working in several iterations to deliver the first version (MVP) with the provided designs as soon as possible.

As for technologies, we decided to use the NextJS framework for server-side rendering of our React components, as SEO optimization was our primary focus. For content management, we used a headless CMS called Prismic so the client can edit the web content and add new language mutations in the future. 

As for styling, we used the TailwindCSS library. For deployment, we first used Vercel, which provided us with a fast content delivery network and a great developer experience. Later, we were assisting the client with deploying the web on its own infrastructure using Kubernetes.

For the Everifin project, we decided to use Kanban to distribute the tasks among developers as well as clearly see the entire scope of the project. We regularly presented the progress of our work to the client to make sure that we were on the same page and that the project would be delivered on time.

We knew that the client wanted to grow fast and therefore adding new language mutations to the web was very crucial for Everifin and needed to be done as easily as possible. Therefore, we invested time to reveal the best possible solution given the limited resources. 

We managed to develop the website structure so that every time the client wants to add a new language mutation, it can be created based on any other language mutation. This means that the client does not have to start from scratch (with no content) but they can just rewrite the content to the desired language. 

Another very challenging thing was to create a component with an interactive map of Europe. This interactive map should enable the user to click a country on the map (or select in a select box), which would show a list of integrated banks in that country (see the screenshot below – screenshot will be provided). The most important thing was that the client could manage the integrated banks and active countries in Prismic. Thanks to Prismic, we managed to meet this requirement easily. 

With limited resources, we managed to create a new presentational website for Everifn in just a month. We created a simple way to manage content on the web, create custom pages and create new language mutations. We used proven (but modern) technologies to finish the project ASAP. Thanks to precious technical documentation and great designs provided by the client, we were able to develop the website quickly. The result is a great-looking presentational website as the client wished. Everifin can now reach people and bring them on board, or simply express itself.

Creating a presentational website isn't not a big deal. However, building a website that would generate awareness, leads and sales, and boost market expansions using multiple language mutations in such a short time, was quite a challenge.

We built a new presentational site for Everifin that is available in multiple language mutations – the client can update them without coding anytime. Read more!

Creating a new Everifin site in multiple languages | Webscope.io

1 month

Page templates

Hazelcast focuses on delivering the most scalable in-memory data grid on the market. The company has released more technologies but what remains the backbone product is Hazelcast IMDG (in-memory data grid) with its Management Center portal. 

The MC portal had been developed by a small internal team in Hazelcast using Java and JavaScript with a gradually outdated version of jQuery. As the company grew, the maintainability of the front-end stack degraded. Costly bugs started to appear, which made it difficult to continue delivering new features. At that point, it made sense for Hazelcast to delegate its front-end development to a dedicated team. 

After initial project discussions, it was clear that Webscope would be the right partner for Hazelcast and so Webscope stepped in the project. 

The main goal was to iteratively refactor the existing code-base from jQuery to an up-to-date frontend stack that is easy to maintain, extend, test and delivered gradually along with new features.

Since we needed technologies that would enable us an incremental refactoring approach, we chose React, Redux and RxJS as the core technologies to build on, while incrementally integrating TypeScript. 

We did a thorough analysis of the jQuery stack that revealed that the code-base was large and the code-style was generally imperative. The size of the code-base meant that planning would play a major role in the overall refactoring process. We identified that the first refactoring iteration should consist of refactoring the router. 

This step gave us a solid and stable foundation to mount existing modules into and also allowed us to tackle the problem truly iteratively, module-by-module.

As for the code-style, the best assurance to migrate complex imperative code is to use test-driven development and replace the complex, imperative constructions with more concise and readable declarations. Functional and declarative library Ramda.js helped us greatly achieve it.

We managed to migrate the whole code-base within one year. We have continued extending the project by adding new features ever since while also focusing to improve the test coverage greatly. We are currently a part of a medium-sized team.

We communicate with Hazelcast on a daily basis. We attend their daily standup calls, where we discuss the progress, the direction of the project and brainstorm new ideas with Hazelcast project management and the rest of the developers. We also hold weekly standups calls to summarize the overall progress. Since the project is large, there are several developers working on the project right now at Webscope, who collaborate with Hazelcast’s own front-end team. From Webscope’s side, the project is managed by tech-lead Honza.

The biggest challenge was the size of the existing code-base. The code-base was large, written imperatively and filled with tricky globals. Moreover, it lacked any unit, integration or end-to-end test coverage whatsoever. No questions asked about type safety. This meant there was no safety net we could utilise during the migration.

It was our task to approach the refactoring rigorously and diligently. We had to dive deep into the project in order to be able to create our own safety net. In such cases, it’s crucial to plan the process well and utilise test-driven development to ensure no runtime bugs are introduced. Looking back, we managed to plan the overall refactoring project well, in order to unlock easy follow-up with new features.

Both Hazelcast and Webscope have come a long way since the start of the cooperation in 2017. We have grown from a one-man team to being a part of the structured Management Center team that counts around 10 members to this date. We have refactored the large code-base, delivered many features and there is more to come in the future. Webscope has become a part of not only the Management Center project but is also solely responsible for front-end development on Hazelcast Cloud.

We have iteratively refactored the existing code-base from jQuery to an up-to-date front-end stack using React@16, TypeScript, Redux and RxJS. Check the outcome.

We have refactored the existing code-base from jQuery to an up-to-date front-end stack using React, TypeScript, Redux and RxJS. Check the outcome.

Refactoring Hazelcast MC's Large Code-Base | Webscope.io

To migrate large-scale code-base to SotA solution

1 year

~1300 tests

0% to 60%

It's a project that we have created in cooperation with the Czech Law firm V4 Legal during the coronavirus times. JakNaCovid is a simple calculator which after answering a few questions about your employment, entrepreneurship, and some other details, will tell you what government financial aid you could claim due to the coronavirus.

Together with V4 Legal, we realized that the Czech government was introducing one government financial aid after another with continuously changing the conditions about who is eligible for the financial assistance and who isn't. 

There were lots of questions and uncertainty out there - people didn't know and couldn't easily find out what financial aid they could claim. Therefore, we decided to act quickly and help people get an overview of all of the government's financial benefits (aid) in one place.

As for the tech-side, the project didn’t bring a challenge we weren’t prepared for. Both the design and implementation stages proceeded smoothly. We were able to iterate a production-ready application with our partners at V4 Legal within a week.

As this project was all about timing - therefore quick delivery - the most challenging part indeed was developing a good-enough and well-arranged framework. A framework that would enable a non-IT person (a law expert) to describe a decision process the customer would be able to follow to retrieve the most helpful information on time.

We ended up designing a decision-tree framework, that allowed our partners at V4 Legal to describe the decision process using a set of nested questions and conditions, to achieve the desired result.

An interesting fact is, the decision tree, as well as condition set files, were each more than a thousand lines long. This is a great reflection of the very complex real-world system of crisis management in the Czech Republic.

The JakNaCovid project has been partially managed by the Webscope development team, and partly by the V4Legal team. Webscope was responsible not only for the development and design, but we also contributed by spreading the word about the project. Thanks to great teamwork, collaboration, and communication with V4 Legal, we managed to get JakNaCovid to multiple websites supporting entrepreneurs, official associations, and to sites about the law. The Czech Ministry of Industry and Trade has also tweeted JakNaCovid on Twitter.

Looking back, we perceive the project as one big success. Given the fact that we didn't have much time and wanted to launch the project as soon as possible, we did a great job together with V4 Legal. We hope that we managed to help people find out information much easily about government financial aid.

We created a covid calculator together with V4 Legal, which helps people find out what government financial aid they can claim due to the coronavirus.

We created JakNaCovid together with V4 Legal which helps people find out what government financial aid they can claim due to the coronavirus. Learn more!

Bringing JakNaCovid.cz Project to Life in a Week | Webscope.io

1 week

2K+ visitors

Tweeted by

Logical Plan searched for a reliable software development partner that would realize the entire mobile app development (iOS and Android) for its project management tool. After the first project discussions, it was clear that Webscope had the right technological and project management experience to implement the project. 

Logical Plan's web application and backend solution had been already done partially by its internal team, and partially by an external software development company. There was a need to use similar technologies to those used for the website platform development to unify the tech stacks and secure the possibility of code sharing. Last but not least, Logical Plan had a limited budget for the app development. For Webscope, it was a challenge to build the mobile application due to the above-mentioned limitations and a tight schedule.

Since there were some client's requirements for the technologies, we did not have that many options. Therefore we used React Native, TypeScript and Mobx. 

The entire project was split into several milestones with a couple of teams working on the project together. Thanks to React and Storybook we were able to work on the business logic and the routing on one side, and on the presentation components on the other site without almost any complications. The project was moving forward at a great pace owing to the chosen technologies and the overall project management.

Due to limited time resources, we had to plan the entire project very thoroughly to make sure that the app was released in time. Thanks to Tomáš's and Marek's planning skills we launched the first version without any delay and in the agreed scope. The LogicalPlan project is mainly under Tomáš's control from the technical point of view. Tomáš communicates with the clients and external backend team about anything related to the development. Marek, our project manager, is also involved in the project discussing mainly the business issues.

The biggest challenge was communication. Since there were a couple of teams (internal and external) working on the website platform and backend, it was quite difficult to keep all people in the loop. Specifically, the most common challenge we faced was cross-platform communication (web requirements for backend vs. mobile app requirements for backend). It happened from time to time that we had to fix bugs that were reported in the mobile application due to changes on the backend. 

However, the decision to use TypeScript turned out to be literally lifesaving. It always showed us issues with incompatible data types after the changes in advance so that we could fix them before the release. This helped us save valuable time and work more effectively.

We managed to deliver the mobile application (for both iOS and Android) in the agreed scope and in time. Since there was a slight delay in the release of the web platform, we gained some extra time to develop more additional features. 

We regularly hold calls with the LogicalPlan to make sure that everything goes smoothly according to the plan. We also provide the client with suggestions and recommendations for potential improvements in terms of technology, backend and user experience (e.g. push notifications).

We built a LogicalPlan mobile application (iOS and Android) in React Native with a limited budget and tight schedule. See how we managed to succeed.

We created a LogicalPlan mobile app (iOS and Android) in React Native with a limited budget and tight schedule. Learn more about the entire project.

Building LogicalPlan app from the ground up | Webscope.io

2 months

Used for reducing cross-platform communication issues

Typescript

60+ companies

Gritera searched for a software development company, which would build a presentational website for their consulting business. The Gritera website should be elegantly designed with a new visual identity and easily editable so that Gritera could itself manage most of the content on the website independently of the developers. Furthermore, since Gritera is running the business in multiple markets, one of the requirements was also to have the website available in various languages. After initial discussions with Gritera about the project, we knew that the time to develop the website would be very tight and challenging for us. 

Based on the project requirements mentioned above, we were searching for a solution which would meet all of the requirements effectively. Therefore, we decided to choose a CMS (content management system) called Prismic - a headless CMS - which means that you get the content in the form of data from the API. Rendering the data itself is then up to the developer. This CMS has a very user-friendly interface for editing content with multiple ways of defining the structure of the content. Since we already had some experience with Prismic on previous projects, it seemed to be the best choice for Gritera as well. 

For the development part, we decided to rely on one of our favourite technologies Next.js framework. It's a React.js framework that is server-generated. It's very comfortable to work with this framework. Plus it offers solutions to the requirements of the project: multi-language rendering and content edit preview. Besides this, Next.js has another great feature which is the static generation. It means that pages are generated during the build time and served as plain HTML files. This process significantly speeds up the loading time of pages, which is crucial for a great user experience in the first place, and SEO (search engine optimization) as well. 

For the visual aspect of the website, we used a library called Tailwind CSS. This library includes predefined classes, which each of them has a specific purpose. It means that you don't have to define any CSS classes. You only need to assign classes to your HTML elements. There is a way to customize the values behind classes (such as sizes, colours, responsive breakpoints) or add additional ones to fit the needs of the specific project. During the production build, project files are scanned, and the final CSS file is stripped of the unused classes to save space and speed up the loading time of the entire website. 

For the deployment of the website, we used a service called Vercel. It supports Next.js, and you can easily preview your work live on the website through it. The setting up is straightforward. You only need to connect the GitHub repository and push code to a branch. Vercel manages the rest. It's a very delightful service to work with since we were able to develop, ask for feedback and fix things very quickly.

To begin with the design process, we compiled the materials from the client and started with the first proposals of the logo. We worked mainly with the company name and its origin (Grit = Guts), the industry, key demographics, target group, company vision and values. 

The main goal was to create an elegant and minimalistic logo with a corresponding web design that creates Gritera's brand image as a reliable partner for larger Norwegian companies that provides a home and nurtures the best management and technology advisors. 

We were working with a few concepts that would represent the values and would create the desired brand image in the target audience. We wanted to stay away from extensive use of colours and non-conform shapes.

We created a logo which follows a minimalistic design with dark font and only one other colour – strong orange. We choose orange because it carries a two-fold meaning:

A combination of energy and happiness, transforming into creativity and passion (company values).

The second meaning one comes from heraldry, where orange is a symbol of endurance and strength displaying perseverance (company value) in your activities. 

The square shape around the first letter symbolizes a home (relates to company vision) - a place that provides you with security and trust. It is a home of professionals that can take you on the road to achieve your goals and dreams. This road is represented by slightly moving the letter G to the right within the square.

After we delivered the logo, we focused on the online presence of the Oslo-based new consulting company. The design process for the static website went pretty fast, and after a few rounds of feedback on prototypes in Invision, we were ready to start the development. Even though the development was done in-house, we decided to create a simple style guide to follow the same patterns and to use consistent elements throughout the web. It is always good to have this kind of document (mostly for larger projects) as one source of truth whether you need to make a few changes or further develop the product. 

The biggest problem that we faced was how to solve the project structure for multiple languages. To be more specific, to find a solution to be able to set different slugs for each language mutation. On the website, there is a page hierarchy, where some pages had multiple slugs combined in the url. These pages need to be aware of the parent page and its slug. The language switcher also had to be aware of the slugs and their combinations.

All in all, the problem itself wasn't much about the implementation as more about the time pressure. Plus, the requirement for the feature was injected into the development process in the last phases, therefore the project structure was incompatible with the suggested solution and had to be redesigned. 

After assessing the possible solutions, we completely rewrote the pages folder and file structure in the codebase. Previously, we had a separate folder for each parent page with its children inside. The new solution is about having one file for the homepage, one file for the parent pages and one for the child pages. The content of the previous files is now rendered conditionally based on the slugs in url.

With limited time, we managed to build a completely new website with a brand new visual identity for Gritera. Thanks to the excellent team cooperation at Webscope, the overall project management, and smooth collaboration with the client, we were able to deliver the multilanguage website in time. We hope the new presentational website will help Gritera boost their business considerably. 

In limited time, we built and designed a multilanguage website using a headless CMS, Next.js, Tailwind CSS, and Vercel for the deployment.

In limited time, we built and designed a multilanguage website using a headless CMS, Next.js, Tailwind CSS, and Vercel for the deployment. See the outcome!

Building & Designing Gritera Multilanguage Website | Webscope.io

Built with

Completely new

License.sh serves as a continuous integration tool that aims to ensure license compliance of a codebase. It is accessible both as a configurable OSS package and as a SaaS web platform which requires a few clicks to get running as it provides seamless integrations with both GitHub and GitLab. While the OSS package focuses on configurability, the web platform is all about simplicity, ease of use and education in the field of software licensing.

We’ve decided to build License.sh due to both internal and our customers' demand. Before developing License.sh, we spent a considerable amount of time implementing and maintaining various license compliance and third party license extractor scripts. It made sense to us to resolve the problem and package it as a dedicated service so that everyone can enjoy a tool that's always ready within the given CI/CD pipeline.

Besides, every developer or project manager who’s ever had a chance to encounter licensing (both in the startup and enterprise world), sooner or later finds out that it’s not straightforward to stay compliant. Especially today when OSS world where not every package maintainer takes proper care of their creation’s licensing. License.sh aims to help even with that.

License.sh core functionality is encapsulated in an OSS tool written in Python. This tool does all the heavy lifting of the license check itself and is powerful enough to provide a complete tooling as for licensing compliance. However, it’s the due diligence of the user to understand the licensing problematics, configure the tool accordingly and deploy it as a part of CI/CD.

Ultimately, that’s why we decided to create a complete easy-to-use SaaS platform. The platform is built on top of the OSS tool, which helps the user understand licensing better, navigates them to create a tailored compliance environment and most importantly, makes the user stay safe.

The platform itself is built with React and Typescript. We have an easy and fast development environment, with the power of Vercel deployment and their Next.js SSR tooling.

The biggest challenge was to run the tool itself in a secure and conternaized environment so that we are sure that the results are safe, consistent and reliable. We managed to do that with the power of Docker and AWS (CodeBuild, S3, Lambda, …).

The license check infrastructure is quite complex, however seamless user experience is a must-have. We’ve spent much time iterating the UX to achieve smooth synchronization of providers API (Github, Gitlab), check runtime and UI. Google’s Firestore managed to be a great help with that. 

As for the payment system, Stripe has become a SOTA solution. Their excellent developer-focused environment is hard to substitute.

We've decided to build License.sh in a lean and customer-driven manner. Considering this and the fact of having only a small team, the project management has to be agile.

The core person that does all the heavy lifting is Bogdan Sikora, who currently works on the project full-time. He manages to cover all the demands as they come on both OSS and the Web platform side.

While the OSS package is meant to live it’s own lifecycle in the OSS world, the web platform, (which aims to be the all-in-one license compliance hammer) is a subject to standard project management practice.

License.sh is a small startup, quickly built and driven by customer demand. We’ve managed to deliver the POC within 6 months and continued with the development for a couple of months to release the first version. We're confident to say, it’s likely the leanest startup product we’ve built so far as for both features and budget.

Available as a configurable OSS package as well as SaaS web platform, License.sh helps you with compliance of your codebase.

License.sh aims to ensure that your code-base is compliant. Right now, available as configurable OSS package as well as SaaS web platform. Learn more here.

Check Your Licenses Instantly with License.sh | Webscope.io

SaaS web application

Vercel’s Next.js

GitHub and GitLab

Founders of Staffers had a clear vision - to improve the conditions in the hospitality industry. They prepared a thorough specification of both mobile and web applications which would help connect staffers (as they call hospitality workers) with hospitality establishments. After meeting the Webscope team at Web Summit and first initial project management discussions, it was clear that Webscope would be a great partner to provide a complete solution. 

The task was clear - to develop a scalable mobile application (both iOS and Android) and a web-based admin application in less than four months. Thanks to clear communication and hard work, we have managed to meet the deadline and deliver exceptional results. Since then a lot has changed. Staffers received funding, and their platform is used all over Oslo. We are glad to be part of this journey, and we continue to develop the mobile application and provide more features and functionalities to the end-users.

First, we evaluated the project specification. When we considered the time frame (4 months) in which it has to be ready, the scope of the application, and the functionality it should provide, we decided that the best tool for this job would be a combination of cross-platform development via React Native for mobile and React for the web. As a backend, we went with server-less architecture with Firebase - Cloud Firestore provided both efficiency and real-time; both things we needed. It allowed us to cut a lot of overheads with cross-platform development and we benefited greatly from Firebase functionalities. We have also used Detox for end-to-end testing, Gatsby for developing the original web page, Typescript to do type checking, and Jest for unit tests. Now, as we scale and grow, we dedicate more and more time to analytics so that we can make informed decisions based on user behavior.

Our Tech Lead Oliver manages the Staffers project. He holds regular meetings with Staffers CTO and shareholders to report what has been done and to discuss what the next steps and priorities are. He also delegates the responsibilities within the team at Webscope, discusses encountered problems during the development to further extend knowledge in the team. Our project manager Marek is also involved in the project, addressing mainly the business side of the project.

The biggest challenge was communication. A precise task specification, understanding the priorities and underlying logic behind some decisions can sometimes be very tough. Some things are apparent from a developer's perspective, others from a client's perspective.

We had to find an effective solution to this challenge quickly to secure the smooth progress of the project. Therefore we started talking more about tasks that might not seem that important and also assigned priority level to all tasks. We also discussed new functionalities and what challenges might occur along the way. Once both parties are on the same page, everything becomes easier.

Staffers have helped find a suitable worker for thousands of positions in the hospitality industry. We are glad that Webscope was able to be part of this journey and that we continue to help Staffers expand.

We have built the entire platform and help Staffers whenever they have questions about what might be possible and what might not. We also provide metrics, help better understand user's behavior, and on top of that, we are here to provide Staffers with our expertise in building startups.

We've built Staffers web and mobile app by utilising cross-platform development in React & React Native and server-less code architecture with Firebase. Read more about the entire project.

We built the Staffers app by utilizing cross-platform development in React & React Native and server-less code architecture with Firebase. Check it out.

Building Staffers Platform From Scratch | Webscope.io

3,5 months

4+ stars

20k+ downloads

Scrumie is a team overview tool that makes the team management things much easier. A transparent overview of the teamwork done based on virtual daily stand-ups is the core feature in Scrumie. Thanks to the availability and time zones, teammates can see when their colleagues are working - via their status availability (vacation, home office, sick day…), as well as their working hours. Two integrations - Slack, Github, and two custom apps (Reporting, Accounting) helps further enhance Scrumie’s functionalities (and more is coming soon!).

There were a couple of reasons that led us to develop Scrumie. Since we couldn’t find a suitable tool that would provide us with the features mentioned above, we decided to invest our resources in developing our own software tool. Actually, it wasn’t the only reason. Learn more about them on Scrumie blog.

Initially, we didn’t plan to make Scrumie public. The user interface and the functionalities were meeting just the basic internal needs. However, after introducing the tool to a couple of companies, we realized that Scrumie might help them with team management as well.

Since we saw an opportunity there, we decided to move Scrumie on a much better level and build a proper software tool out of it.

We applied for Web Summit 2019 in Lisbon, where we presented Scrumie as an alpha-startup. It turned out to be a great step because we validated Scrumie’s main idea and gained valuable feedback from our early adopters. 

Since then, we are still improving Scrumie, adding new features & integrations and working on the marketing & sales part.

For the entire tool development, we decided to rely on our very favourite technologies and frameworks. For the backend part, we chose Django with PostgreSQL database and for front-end React with Typescript that we also use on many clients’ projects. Client-server communication is built with GraphQL middleware: Graphene library on the back-end side and Apollo Client on the front-end. We use CMS Django for managing and writing the blog posts. So far, we have managed to integrate Scrumie with these four commonly used tools:

All of the integrations are using OAuth authentication connecting Scrumie application with Scrumie users' accounts and workspaces. It is still Django under the hood on our side to process such things. Trello, Jira and Slack communication is built on REST, for GitHub we are fetching data via their GraphQL layer directly from the Scrumie client.

Since every service (integration) has differences in the scope of how they work (such as data flow, APIs, main ideas they are following, etc.), it is challenging to cover them under a mutual UI and implementation paradigm.

Ideally, the implementation of integrations should be wrapped up with a common abstraction serializing everything into an output of the single type for scalability purposes. However, we decided to skip this challenging part temporarily to speed up the integration process of the most commonly used tools on the market.

On the #1 place are our clients. Therefore we don’t devote Scrumie that much time as we wish to. However, with great people and planning, we’ve made great progress so far. We run 14-day sprints, not only in the development, but also in other parts such as design, marketing and sales. We do our best to interconnect the activities across the multiple areas to make sure that the teams are on the same page. This approach enables us to act agilely and plan further functionalities and steps more efficiently.

So far, we have done a beautiful design, developed two custom apps, released two integrations, added more features and more is coming soon.

We’re very glad that we have put so much effort and time into developing Scrumie. We hope that Scrumie will help more companies solve the same problems we had. We’re also very much open to any feedback from your side. If you are interested in trying Scrumie, try our beta version that’s free to use and share any feedback you might have.

Know what's happening in your team thanks to a simple tool that makes the team management things much easier.

Scrumie makes your team stay in the loop no matter where the teammates are working. Virtual stand-ups, transparent work overview and more. Check it out.

See how we are bringing projects to life

Clients projects

WEB DEVELOPMENT

Building a multi-language website for the Slovak Fintech

CODE MIGRATION, DESIGN

Refactoring Hazelcast Management Center's large code-base

APP DEVELOPMENT

Building LogicalPlan app from the ground up

WEB DEVELOPMENT, DESIGN

Building & Designing Gritera Multilanguage Website

APP DEVELOPMENT

Building Staffers platform from scratch

This is a great place for your project

Satisfied clients

Our side projects

WEB DEVELOPMENT, DESIGN

Bringing covid calculator to life in a week

WEB DEVELOPMENT, DESIGN

License.sh ensures license compliance of your codebase

WEB DEVELOPMENT, DESIGN

Scrumie - a teamwork overview tool

Curious about how we work? Check out our project workflow.