About Ivejas
They are a Vilnius-based digital company that creates web applications and mobile applications for clients worldwide. They always strive to know the process in order to produce effective solutions. Their aim from the starting has been to design, develop, and produce solutions that are specific to the demands of their clients.
Services
Ivejas Reviews
Write a ReviewThe outcome we specified, delivered the way we needed it, by people we would hire again
Ji-Woo Park / VP of Engineering - Seoul Digital CorpJun 02, 2026
Project summary: Evolving open banking obligations required us to rebuild our API layer from the ground up. The architecture needed to be compliant by default, not bolted on after the fact.
I came into this engagement as a sceptic. We had been through a failed implementation with a previous vendor and I had high standards for what evidence of competence looked like before I would trust a partner with our core systems. This team earned that trust progressively — through the quality of the discovery documentation, the rigour of the technical proposals, the consistency of the sprint deliveries, and ultimately the stability of the production system. I no longer lead with scepticism when recommending them.
Deep domain knowledge that reduced the discovery overhead significantly, proactive risk identification before issues became incidents, delivery cadence that our stakeholders found reassuring
Time zone coordination required some deliberate overlap management from both sides in the first couple of sprints, after which we had an efficient async rhythm that worked for the whole project
Questions & Answers
Blockchain expertise that came with clear explanations, not just technical jargon
Siobhan Gallagher / Chief Technology Officer - Northumbria FinTech LtdMay 21, 2026
Project summary: Time-to-market for new tariff structures had become a direct competitive disadvantage. Our product configuration layer was the bottleneck and it needed to be modernised as a priority.
Six months after go-live our platform is processing three times the transaction volume we specified in the original brief. The architecture choices made during discovery accommodated that growth without remediation work. That is the difference between a team that designs for what you tell them and a team that designs for what you are likely to need. We are in conversation about a Phase 2 engagement and I expect to be using this partnership for several years.
Senior-level engineering presence throughout the entire project, not just during the pitch, honest and commercially fair handling of scope changes, codebase that our internal team praised on review
Their discovery process is more rigorous than we were accustomed to and required more preparation from our side than we had initially allocated — but the quality of what followed justified every hour of it
Questions & Answers
Security posture transformed from a known liability to a competitive differentiator
Zofia Kamińska / CTO - Odra Tech StudioMay 14, 2026
Project summary: Our engineering capacity was committed to maintaining existing systems and could not absorb a net-new build of this complexity. An external partner with the right skills was the only viable option.
What made the most difference in practice was the quality of the engineering judgment on this team. Not the ability to execute a specification — that is a baseline expectation. The ability to recognise when a specification was suboptimal, explain why, propose an alternative, and support the client in making a decision about it. That consultative dimension elevated the output beyond what the brief described and resulted in a product that is more fit for purpose than the one we had originally specified.
Delivery timeline that proved achievable rather than optimistic, estimation accuracy that reflected real analysis rather than competitive bidding, scope discipline that prevented the feature creep we had experienced before
The quality of documentation they produce means our team needed to set aside dedicated review time to do it justice — a minor scheduling point rather than a genuine criticism
Questions & Answers
Infrastructure-as-code that our SRE team treats as a reference example
Rupert Ashford / Director of eCommerce - Hargrove Retail PLCApr 20, 2026
Project summary: Track-and-trace capability had gone from a differentiator to a table-stakes requirement and our platform had neither. We needed to close the gap before our next enterprise tender cycle.
The project brief was ambitious and we had received proposals ranging from two to five times our eventual budget from other vendors. This team came back with a proposal that was commercially realistic and technically credible — and then delivered against it. That alignment between proposal and outcome is not something I take for granted. I have been on the other side of it enough times to know it requires both honesty in the sales process and discipline in delivery. We experienced both.
Collaborative culture that made the team feel like a genuine extension of our organisation, strong asynchronous communication across time zones, zero-drama handling of the inevitable mid-project changes
Pipeline availability for kickoff required a few weeks of lead time — in hindsight that selection pressure means you are working with a team that is in demand for the right reasons
Questions & Answers
Real-time dashboards that our executives now open before any other application
Shreya Krishnaswamy / VP of Product - Luminar Tech Pvt LtdApr 13, 2026
Project summary: Our engineering capacity was committed to maintaining existing systems and could not absorb a net-new build of this complexity. An external partner with the right skills was the only viable option.
The integration layer was the part of the project I was most concerned about going in. Our system landscape is complex, several of the upstream APIs we relied on were poorly documented, and two third-party vendors had a history of unpredictable response times on integration questions. This team managed all of that. They documented what the upstream vendors could not, built resilience into the integration architecture where the upstream behaviour was unreliable, and delivered a solution that works as specified in production. I could not have asked for more.
Commercially transparent throughout — no hidden assumptions, no bill shock at the end, change requests that were fair and clearly explained rather than used as a margin-recovery mechanism
Their discovery process is more rigorous than we were accustomed to and required more preparation from our side than we had initially allocated — but the quality of what followed justified every hour of it
Questions & Answers
Data engineering quality that will support our growth for years without a rebuild
Yuki Hashimoto / Head of Product Development - East Asia Commerce KKApr 10, 2026
Project summary: Several years of incremental development had left us with a platform that was technically functional but strategically limiting. A structured rebuild was the agreed path forward.
The project brief was ambitious and we had received proposals ranging from two to five times our eventual budget from other vendors. This team came back with a proposal that was commercially realistic and technically credible — and then delivered against it. That alignment between proposal and outcome is not something I take for granted. I have been on the other side of it enough times to know it requires both honesty in the sales process and discipline in delivery. We experienced both.
Architectural decisions designed for longevity rather than just the current brief, thorough automated test coverage, post-launch stability that validated every technical choice made during discovery
The quality of documentation they produce means our team needed to set aside dedicated review time to do it justice — a minor scheduling point rather than a genuine criticism
Questions & Answers
Performance testing that identified a bottleneck hiding in plain sight
Faisal Al-Ghamdi / Chief Digital Officer - Riyadh Tech VenturesMar 21, 2026
Project summary: Our institution was running five disconnected systems for admissions, learning management, assessments, and student communications — we needed them unified into one cohesive platform.
The engagement started with a discovery workshop that immediately signalled this team was different. They pushed back on two of our assumptions in the first session with evidence and a better alternative. That kind of intellectual honesty is rare and it set the tone for the whole project. Deliverables were consistently ahead of schedule, code reviews were taken seriously, and the final product is something we are proud to show enterprise clients during due diligence calls.
Business-aware approach to every technical decision, strong project governance, fast turnaround on feedback, zero drama during a genuinely complex engagement
Honestly nothing worth documenting — we went in with high expectations and they were met on every measure
Questions & Answers
AI models that replaced guesswork with evidence in decisions that matter most
Eoghan Fitzgerald / VP of Engineering - Shannon Tech Solutions LtdMar 17, 2026
Project summary: Our internal product thinking was strong but our execution capability in this specific technology domain was limited. We needed depth, not generalism.
The project brief was ambitious and we had received proposals ranging from two to five times our eventual budget from other vendors. This team came back with a proposal that was commercially realistic and technically credible — and then delivered against it. That alignment between proposal and outcome is not something I take for granted. I have been on the other side of it enough times to know it requires both honesty in the sales process and discipline in delivery. We experienced both.
Deep domain knowledge that reduced the discovery overhead significantly, proactive risk identification before issues became incidents, delivery cadence that our stakeholders found reassuring
Time zone coordination required some deliberate overlap management from both sides in the first couple of sprints, after which we had an efficient async rhythm that worked for the whole project
Questions & Answers
QA coverage that finally made Friday deployments feel like a professional activity
Omar Al-Farsi / Chief Technology Officer - Falcon Digital VenturesMar 04, 2026
Project summary: Our engineering capacity was committed to maintaining existing systems and could not absorb a net-new build of this complexity. An external partner with the right skills was the only viable option.
Our stakeholder group included board members, clinical leads, compliance officers, and end users — each with different technical literacy and different success criteria. This team navigated that stakeholder landscape as well as any vendor I have seen. They adjusted their communication register depending on the audience without losing the substance. They managed expectations honestly throughout. And they delivered a system that each group can point to as meeting their requirements. That breadth is genuinely uncommon.
Commercially transparent throughout — no hidden assumptions, no bill shock at the end, change requests that were fair and clearly explained rather than used as a margin-recovery mechanism
Their insistence on a detailed functional specification before development began felt like friction at the time. In retrospect, it was the reason the development phase ran without the ambiguity that has derailed similar projects for us previously
Questions & Answers
Predictive models that have measurably changed how we approach every planning cycle
Yuki Hashimoto / Head of Product Development - East Asia Commerce KKFeb 06, 2026
Project summary: Remote care had gone from an experiment to a core service line and our technology had not kept pace. We needed a robust, compliant telehealth platform in a timeline that the market would not wait for.
What made the most difference in practice was the quality of the engineering judgment on this team. Not the ability to execute a specification — that is a baseline expectation. The ability to recognise when a specification was suboptimal, explain why, propose an alternative, and support the client in making a decision about it. That consultative dimension elevated the output beyond what the brief described and resulted in a product that is more fit for purpose than the one we had originally specified.
Clear and consistent communication adapted appropriately for both technical and non-technical stakeholders, shared tooling that gave our team real-time visibility, reliable sprint delivery throughout
Their discovery process is more rigorous than we were accustomed to and required more preparation from our side than we had initially allocated — but the quality of what followed justified every hour of it
Questions & Answers
Project execution that matched the proposal in every dimension that mattered
Priya Chandrasekaran / VP of Data & AI - Wavefront Analytics IncFeb 06, 2026
Project summary: The project had a board-facing delivery date tied to a strategic initiative. We needed a partner who would treat that date as their own, not ours.
The technical quality of the final deliverable is the easiest thing to point to. The automated test coverage is thorough, the deployment pipeline is reliable, the documentation is genuinely useful rather than ceremonially produced. But the metric I keep returning to is the number of post-launch conversations we have not had to have. No incident calls at two in the morning. No emergency patches. No retrospective discussions about what went wrong. The absence of those events is the evidence I would show to someone considering this vendor.
Delivery timeline that proved achievable rather than optimistic, estimation accuracy that reflected real analysis rather than competitive bidding, scope discipline that prevented the feature creep we had experienced before
Their discovery process is more rigorous than we were accustomed to and required more preparation from our side than we had initially allocated — but the quality of what followed justified every hour of it
Questions & Answers
From proof-of-concept to production AI in a timeline that impressed our board
Khalid Al-Mansoori / Chief Digital Officer - Emirates Digital GroupJul 16, 2025
Project summary: Remote and hybrid learning had exposed the limitations of our existing LMS and we needed a purpose-built solution that could scale to 50,000 concurrent users without degrading the experience.
I am a demanding client. I have a technical background, I review code, and I have high standards for documentation and testing. This team met all of those expectations without ever seeming defensive about scrutiny. Peer code reviews were welcomed, unit test coverage was genuine rather than performative, and the API documentation was thorough enough that our own developers integrated against it without a single clarification call. That level of craft is what I look for and rarely find.
Engineering quality that our internal team can maintain without calling the vendor, thorough documentation, proactive risk identification throughout the project
We underestimated the internal resource commitment required on our side during discovery — the team warned us, we did not listen fully, and the first sprint was slower as a result
Questions & Answers
A mobile app our customers downloaded and never deleted
Lachlan Burgess / Chief Digital Officer - Harbour Digital Pty LtdAug 13, 2022
Project summary: The project had both a hard delivery date tied to a board commitment and a scope that our previous agency had told us was not achievable. We needed someone to prove otherwise.
The engagement started with a discovery workshop that immediately signalled this team was different. They pushed back on two of our assumptions in the first session with evidence and a better alternative. That kind of intellectual honesty is rare and it set the tone for the whole project. Deliverables were consistently ahead of schedule, code reviews were taken seriously, and the final product is something we are proud to show enterprise clients during due diligence calls.
Architectural decisions that will serve us for years rather than just solving the immediate problem, knowledge transfer that left our team genuinely capable, no scope creep at all
Time zone difference required some adjustment to our internal communication habits but the team managed the overlap window efficiently and it never affected momentum