Build
Faster.
Full code RAD platform with predefined modules and all around infrastructure to launch your high quality products to market in no time.
Common Development Issues
Time to market
Technology stack
Architectural designs
Software quality
Development methodologies
Software lifecycle
Documentation
Onboarding
Sometimes all you need is Warp Stack
Warp stack is the result of our long-time experience and knowledge in software development and it consists of software methodologies and software development best practices .
What’s in the Stack?
Methodologies
Infrastructure
FIYU Platform
Modules
Platform Management Module
Organization Management Module
User Management Module
Notification Management Module
E-mail Management Module
Document Management Module
A module whose purpose is to manage the entire platform and all other modules. Only the owners of the platform have access rights to this module.
A module used for management within the organization, its structure and organization, employees, and the entire account management within the platform.
A module in which an organization manages all its platform users, their rights, permissions, and roles.
A central place for all notifications within the platform, user or system, and their management.
A central place for all emails within the platform, user or system, and their management.
A central place for all documents within the platform and their management.
Speedy platform. Serious business.
Get the no-hassle custom software in the shortest time possible with FIYU. By using high-productivity tools and methodologies, developers can build apps faster. Which in the end means saving YOUR money.
Speed up your time to market
Save your money and forget about never-ending app development.
Features
General infrastructure
- Platform Management
User Management
Organization Management
Notification Management
Email Management
Document Management
Multitenancy
I18n/l10n
Time zone independent
High Availability/ Continuous Availability
- Multi-Model
RDBMS
Multi-Model
Versioning
Dependency management
Code Quality
User preferences
Module settings
Push notifications
Frontend
- Automated Dynamic form creation
Modules versioning
DTO versioning
CRUD operations
TASK UI ready
Advanced Data Grid
- Fully customizable layouts and components
Enhanced and responsive UI/UX
- Fully customizable, multiple themes
User preferences
Module settings
Push notifications
Backend
- ACL
GDPR ready repository
AUDIT ready repository
CQRS ready
Languages agnostic programming
- Third party (LDAP, KeyCloak, AD)
- Module lifecycle management
Module settings
User preferences
- OpenAPI / Swagger
Security
Logging (ELK)
Monitoring
Real stories from real customers
During my daily work with the team, their professionalism, experience and reliability became noticeable
Tomaž Šarc
Project manager at Epilog d.o.o.
With new requirements, challenges, opportunities, rapid technology development we looked for additional knowledge and experience outside, to complement and modernize our products & solutions to deliver best possible customer experience. We have found a team, which consists of highly knowledgeable and reliable individuals who are always ready for any challenge at any time.
Matej Stipič
Head of Atlas Department at Epilog d.o.o.
Potential customer:
A startup with initial funding, aiming to build a B2B platform for supply and demand of industrial manufacturing.
What they need:
They are planning to develop a modern, scalable, and robust platform. Modern architecture is a must, but they also need to use the best practices of project management and DevOps. Because they are building from scratch, it is not only important to provide an agile approach but to document and perform automated testing. This is mandatory. Documentation is necessary because they plan to onboard additional developers over time, as the platform will grow. The platform must be installed on AWS.
What we propose:
We propose FIYU with a small delivery team of five people (1 tester/product owner, 2 frontend and 2 backend developers). The delivery team will tightly cooperate with the customer’s team, sharing knowledge and expertise. Development will be based on FIYU, which will speed up delivery of the MVP for investors.
Potential customer:
A big enterprise in need of a document management application.
What they need:
They are planning on purchasing a customized application for a specific business process. The required features are defined. The contract will be given to the company which offers the lowest price and the shortest delivery time. The customer will provide all necessary hardware.
What we propose:
We propose a project based on FIYU. Two juniors will reuse the existing features and develop all customized features. The project will be finished in 2 months.
Potential customer:
An IT vendor needs to develop a specific tailor-made application for their customer.
What they need:
The IT vendor lacks expertise in building modern progressive applications accessible from desktop and from mobile. The application was not specified well, but both the budget and the delivery date are fixed.
What we propose:
We propose a project based on FIYU. A small delivery team of three people (1 tester/product owner, 1 frontend and 1 backend developer) with the support of a FIYU architect and a DevOps engineer. At first, the product owner will provide the necessary specifications. After the specifications are approved, the development team will develop the required features in 3 months.
Potential customer:
An IT vendor for an intralogistics WMS needs to modernize their flagship product.
What they need:
The IT vendor – with 30 years of experience in building their product – plans on creating a new version of the product. The current version is rather outdated (a fat client installed on user desktop). It is using monolithic architecture and lots of legacy components that do not provide modern application distribution and access (from Android mobile devices and web browser). They plan to start by rewriting the graphical interface and then incrementally modernize the backend logic (from logic stored in DB procedures to microservice backend). The new version has improved user experience, a limited cost of implementation according to the ‘code once, use many times’ principle, fast and simple development (focused on scalable architecture and proven programming concepts) and it uses modern technologies to attract new developers.
What we propose:
Long-term development based on FIYU. We will provide a scrum team of nine people (a product owner, a frontend, and a backend architect, a DevOps engineer, 2 frontend, 2 backend developers, and a tester). The utilization of a core FIYU team (a product owner, a frontend, and a backend architect, a DevOps engineer) will be for 3 to 4 months. Over this period, the core team will educate the customer’s developer team and transfer best practices and general knowledge of FIYU architecture. After 3 to 4 months, they will return to other projects. The rest of the team will continue working on long-term development of a new generation of the product.
