--- title: "AI & Frontier Technology" canonical: https://wavect.io/services/bleeding-edge/ language: en description: "AI, blockchain, IoT, and zero-knowledge. Wavect ships AI products and emerging-tech systems to production, and tells you when the frontier is the wrong bet." image: "https://wavect.io/img/general/bak/open_graph_preview.jpg" --- AI & Frontier Tech # AI & Frontier Technology, Shipped to Production AI, blockchain, IoT, and zero-knowledge. The hard part is knowing which of these actually earns its place in your product, if any. No hype, just real business cases, and we say so when the frontier is the wrong bet. - 75+ products shipped - 10+ years experience - No-Bullshit Guarantee // 01 ## Where does our frontier expertise sit? If your project needs expertise we do not hold in-house, we say so early and bring in a specialist we have already shipped with. AI Agents & Products We build AI agents, agentic SaaS, and LLM apps that survive production. You don't need to train your own model, you need to use the right one well, and to know when AI is the wrong tool. [Explore AI development](/services/artificial-intelligence/) AI Enablement Adopt AI inside your own team: workshops plus done-for-you setup on your own infrastructure, with cost control and compliance built in. Real relief, not shelfware. [See AI enablement](/services/ai-enablement/) Blockchain Distributed ledgers done right, from EVM and Solana to zero-knowledge proofs. Smart contracts, wallets, and bridges with a public mainnet track record. [Explore blockchain](/services/blockchain/) Internet of Things Smart-city and sensor systems, with deep LoRaWAN experience. Connect hardware, networks, and cloud operations without losing sight of field maintenance. [Explore IoT engineering](/services/internet-of-things/) Zero Knowledge When GDPR compliance is not enough and you want full control over your data. Privacy by cryptographic proof, not policy. [Explore zero knowledge](/services/zero-knowledge/) // 02 ## How do we approach frontier tech? We're not about using tech for tech's sake. Our philosophy is simple: Right Tool for the Job We select technologies based on actual utility for your specific needs, not because they're trending. Focus is always on what delivers the best results. Practical & Results-Focused Functionality and business outcomes over flashy technology. Our solutions are designed to solve real problems and create measurable value. A Measurable Reason to Use It A frontier technology earns its place by lowering cost, removing a constraint, or creating an advantage a mature stack cannot. Otherwise, we use the mature stack. HOW WE DEVELOP SOFTWARE ## How we develop Software Five phases. Fixed prices. No lock-in. Phase 01 ### Discovery Phase Fixed price at 3.500€ [Buy now](https://buy.stripe.com/14k4kbbMJ1unb4I7sw) - Requirements Engineering - Software Architecture - Milestone Plan - Technical Flows and Sequence Diagrams - Launch Plan and Milestone Plan Phase 02 ### First Iteration Fixed price between 15–20k€ (MAX) [Book Discovery Phase](https://buy.stripe.com/14k4kbbMJ1unb4I7sw) - Building your real MAP (Minimal Awesome Product) - Cost-effective approach. Strip requirements to 15–20k max - Test directly on the market as cheaply as possible with real customers - Discovery Phase cost is deducted as a rebate Phase 03 ### Subsequent Iterations Fixed price packages / Agile Fixed Price [What is Agile Fixed Pricing?](/blog/agile-fixed-pricing/) - Building and extending product based on real customer/user demand - Ideally partially funded by real sales - Data-driven development decisions (watch user behavior over user demands) - Continuous improvement cycle Phase 04 ### Maintenance Fixed weekly retainer 750€ / week, cancel anytime [Get in touch](/contact/) - Security patches (nobody likes data breaches or losing money) - Fixing bugs (can be a major reason of customer churn) - Technical support (most companies have an abysmal customer support) - Performance, cost & CI/CD optimization Phase 05 ### Further Dev / Hand-Over Your product, your team. We'll never lock you in. - We'll never make you dependent on our team - Smooth transition to your internal team - Knowledge transfer and documentation - Continued support as needed // proof ## Proof, not promises ### [Account Abstraction](/case-studies/account-abstraction/) - **Status:** Live - **Outcome:** 3 SDKs - Backend · Contract · Frontend - **Summary:** Three-layer Hybrid Compute SDK suite (backend, contract, frontend), built with Boba's team against undocumented infra, still in … - **Stack:** Typescript, Solidity, Hardhat ### [MetaMask Snap](/case-studies/metamask-snap/) - **Status:** Live - **Outcome:** MetaMask - Native Integration - **Summary:** Smart wallets with Hybrid Compute, inside the wallet users already trust, built with Boba's team against MetaMask's Snap sandbox. - **Stack:** Typescript, MetaMask Snaps, Solidity ### [LivLive](/case-studies/livlive/) - **Status:** Live - **Outcome:** +1,000 - Concurrent Users - **Summary:** AR-RWA platform: $2M+ raised through the product, 1,000+ concurrent users, six weeks flat. - **Stack:** Solidity, Typescript, React These are selected projects, not our full portfolio. We have shipped 75+ products since 2018. ### What clients say Trustpilot **A find in a web3 world full of scammers.** Clear and objective communication and final result above expectations. Read more → Tiago Amaral Original LinkedIn **As a non-technical founder, developing an NFT project for our membership DAO, I got in touch with Kevin as we were having some trouble communicating effectively with our internationally located development contractor.** After first conversations with Kevin it became clear that his knowledge would significantly help us in defining, planning and executing our smart contract and NFTs, and working efficiently with the other contractors we had hired. We contracted Kevin to take on the technical project management, and reduce the load on our team. He was extremely easy to work with, always helpful, super responsive, willing to explain things and extremely professional. He very effectively coordinated between various stakeholders in the project and we will definitely be reaching out to him again when we need to develop requirements or have a dApp project managed from start to finish. Thanks a lot for making it happen Kevin. Read more → Isla Munro-Hochmayr Web3 Researcher Original Google **Extensive knowledge and a creative approach.** Extremely satisfied with their professional demeanor. I highly recommend them and look forward to future collaborations. Read more → Mark Cserey Original Independently rated 4.5/5 on Trustpilot [Read the reviews](https://www.trustpilot.com/review/wavect.io) [![Clutch Top Web3 Development in Austria 2026 award for Wavect](/img/awards/clutch-top-web3-development-austria-2026_hu_92ea6d2c36d12863.webp) Verified on Clutch · 2026 Top Web3 Development in Austria View our Clutch profile](https://clutch.co/profile/wavect-gmbh) [![Clutch Top Artificial Intelligence Company in Austria 2026 award for Wavect](/img/awards/clutch-top-artificial-intelligence-company-austria-2026_hu_836f96666ce05e7b.webp) Verified on Clutch · 2026 Top Artificial Intelligence Company in Austria View our Clutch profile](https://clutch.co/profile/wavect-gmbh) ## FAQs When the cutting edge actually pays off ### How does the weekly cancellation actually work? End any week, with one message. No notice period, no exit interview, no fine print. We invoice weekly, so the most you’re ever committed to is the current week. ### What if I'm not blown away by the work? It’s in your contract: tell us, and we refund that week. No questions, no invoices to dispute, no calls to escalate. The only rule: refunds apply to the most recent week. ### Why don't you track hours? Because hours are the wrong metric. If we optimize for hours billed, we do not optimize for your outcome. The deal is simpler: every week has a defined result, and we earn the next week by delivering it. You pay for progress against that result, not for a timesheet. ### What does 'expectations detached from reality' mean? We work with operators, not lottery winners. If a request would require breaking physics, the law, or a third party’s systems, we say so, and if we can’t align, we walk. The guarantee is mutual: you can fire us any week; we can also fire ourselves. ### How do you decide whether a bleeding-edge tech is production-ready? We weigh four things: maturity of the surrounding ecosystem (libraries, hiring market, debugging tools), seriousness of the worst failure mode, presence of an exit path back to a mature stack, and whether the competitive advantage is real or vanity. If three of four don’t pass, we recommend the conventional stack. ### What if the tech we want is still in alpha? We’ll tell you up front and structure the engagement around it: smaller initial scope, parallel safer fallback path, explicit budget for upstream contributions and unexpected work. Alpha-stage tech ships, but only when you scope it like research, not like a delivery commitment. ### Do you take R&D engagements or only production work? Both. R&D engagements are scoped as time-boxed exploration with deliverables (working prototype + written assessment + recommendation). Production engagements have a hard delivery commitment. We don’t pretend an R&D engagement is production work. That’s how teams burn budget for two quarters with nothing to show. ### Who owns the IP from R&D outputs? You do. Standard work-for-hire terms transfer all IP to you on delivery, including R&D outputs. Any open-source contributions we make upstream during the project (often necessary to make alpha tech work) are clearly listed in advance. We don’t quietly ship your code to a public repo without disclosure. ### How do we budget for failed experiments on bleeding-edge tech? Failed experiments are a budget line, not a surprise. For R&D-shaped engagements we typically reserve 20-30% of total budget for ’this didn’t work, try something else.’ If we hit a dead end fast (week one) we tell you and reroute. If we hit it late, the previous learnings still inform the production design we recommend. The worst outcome we plan for: you spend the R&D budget and we hand you a written ‘do not build this’ assessment with reasons. That’s still a real deliverable. // More in ## More in Artificial Intelligence ### [AI Agents & Products](/services/artificial-intelligence/) We build AI agents, agentic SaaS, and LLM apps that survive production, and tell you when AI is the wrong tool. ### [AI Enablement](/services/ai-enablement/) Adopt AI inside your own team: workshops plus done-for-you setup on your infrastructure. No shelfware. ### [Vibe Coding Rescue](/services/vibe-coding-rescue/) Fix vibe-coded and AI-generated apps before they break in production. Audit first, then harden. ### [Internet of Things](/services/internet-of-things/) LoRaWAN infrastructure, multi-vendor device integration, decoders and data pipelines. Software side, not firmware. // Get to know us ## Get to know us Long-term relationships over quick wins. [![Blogs](/img/services/gtku_blogs_hu_d7e3f659443e93f9.webp) Read our Blog](/blog/overview/) [![No BS Around Tech Podcast](/img/services/gtku_podcast_hu_aac94ba51d8a6f9f.webp) No BS Around Tech Podcast](/#trust-podcast) [![Image Gallery](/img/services/gtknu_gallery_hu_451025d2d15b7558.webp) Get some Impressions](/#image-gallery) ## Structured Data ```json { "@context": "https://schema.org", "@graph": [ { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ], "employee": [ { "@id": "https://wavect.io/team/kevin-riedl/#person", "@type": "Person", "jobTitle": "Managing Director", "name": "Kevin Riedl", "url": "https://wavect.io/team/kevin-riedl/", "worksFor": { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] } }, { "@id": "https://wavect.io/team/christof-jori/#person", "@type": "Person", "jobTitle": "Managing Director", "name": "Christof Jori", "url": "https://wavect.io/team/christof-jori/", "worksFor": { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] } } ], "founder": [ { "@id": "https://wavect.io/team/kevin-riedl/#person", "@type": "Person", "jobTitle": "Managing Director", "name": "Kevin Riedl", "url": "https://wavect.io/team/kevin-riedl/", "worksFor": { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] } }, { "@id": "https://wavect.io/team/christof-jori/#person", "@type": "Person", "jobTitle": "Managing Director", "name": "Christof Jori", "url": "https://wavect.io/team/christof-jori/", "worksFor": { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] } } ], "legalRepresentative": [ { "@id": "https://wavect.io/team/kevin-riedl/#person", "@type": "Person", "jobTitle": "Managing Director", "name": "Kevin Riedl", "url": "https://wavect.io/team/kevin-riedl/", "worksFor": { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] } }, { "@id": "https://wavect.io/team/christof-jori/#person", "@type": "Person", "jobTitle": "Managing Director", "name": "Christof Jori", "url": "https://wavect.io/team/christof-jori/", "worksFor": { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] } } ], "name": "Wavect GmbH", "subjectOf": { "@id": "https://wavect.io/verified-claims.json#dataset", "@type": "Dataset", "creator": { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] }, "description": "A machine-readable registry of quantitative and qualitative claims published by Wavect, with review dates, localized page appearances and public third-party citations where available.", "inLanguage": "en", "isAccessibleForFree": true, "license": "https://creativecommons.org/licenses/by/4.0/", "name": "Wavect verified publication claims", "url": "https://wavect.io/verified-claims.json" }, "url": "https://wavect.io/" }, { "@id": "https://wavect.io/team/kevin-riedl/#person", "@type": "Person", "jobTitle": "Managing Director", "name": "Kevin Riedl", "sameAs": [ "https://www.wikidata.org/wiki/Q139796365", "https://www.linkedin.com/in/wsdt", "https://github.com/wsdt" ], "url": "https://wavect.io/team/kevin-riedl/", "worksFor": { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] } }, { "@id": "https://wavect.io/team/christof-jori/#person", "@type": "Person", "jobTitle": "Managing Director", "name": "Christof Jori", "sameAs": [ "https://www.wikidata.org/wiki/Q139796367", "https://www.linkedin.com/in/jocr77/", "https://github.com/jo-chris" ], "url": "https://wavect.io/team/christof-jori/", "worksFor": { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] } }, { "@id": "https://wavect.io/#website", "@type": "WebSite", "inLanguage": [ "en", "de", "es", "zh" ], "name": "Wavect", "potentialAction": { "@type": "SearchAction", "query-input": "required name=search_term_string", "target": { "@type": "EntryPoint", "urlTemplate": "https://wavect.io/search/?q={search_term_string}" } }, "publisher": { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] }, "url": "https://wavect.io/" } ] } ``` ```json { "@context": "https://schema.org", "@graph": [ { "@id": "https://wavect.io/services/bleeding-edge/#service", "@type": "Service", "areaServed": [ { "@type": "Country", "name": "Austria" }, { "@type": "Place", "name": "Worldwide" } ], "description": "AI, blockchain, IoT, and zero-knowledge. Wavect ships AI products and emerging-tech systems to production, and tells you when the frontier is the wrong bet.", "name": "AI & Frontier Technology, Shipped to Production", "provider": { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] }, "serviceType": "Emerging Technology R&D", "url": "https://wavect.io/services/bleeding-edge/" }, { "@type": "BreadcrumbList", "itemListElement": [ { "@type": "ListItem", "item": "https://wavect.io/", "name": "Home", "position": 1 }, { "@type": "ListItem", "item": "https://wavect.io/services/overview/", "name": "Services", "position": 2 }, { "@type": "ListItem", "item": "https://wavect.io/services/bleeding-edge/", "name": "AI & Frontier Tech", "position": 3 } ] }, { "@id": "https://wavect.io/services/bleeding-edge/#webpage", "@type": "WebPage", "description": "AI, blockchain, IoT, and zero-knowledge. Wavect ships AI products and emerging-tech systems to production, and tells you when the frontier is the wrong bet.", "inLanguage": "en", "isPartOf": { "@id": "https://wavect.io/#website", "@type": "WebSite" }, "mainEntity": { "@id": "https://wavect.io/services/bleeding-edge/#service" }, "name": "AI & Frontier Technology, Shipped to Production", "url": "https://wavect.io/services/bleeding-edge/" } ] } ``` ```json { "@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [ { "@type": "Question", "acceptedAnswer": { "@type": "Answer", "text": "End any week, with one message. No notice period, no exit interview, no fine print. We invoice weekly, so the most you're ever committed to is the current week." }, "name": "How does the weekly cancellation actually work?" }, { "@type": "Question", "acceptedAnswer": { "@type": "Answer", "text": "It's in your contract: tell us, and we refund that week. No questions, no invoices to dispute, no calls to escalate. The only rule: refunds apply to the most recent week." }, "name": "What if I'm not blown away by the work?" }, { "@type": "Question", "acceptedAnswer": { "@type": "Answer", "text": "Because hours are the wrong metric. If we optimize for hours billed, we do not optimize for your outcome. The deal is simpler: every week has a defined result, and we earn the next week by delivering it. You pay for progress against that result, not for a timesheet." }, "name": "Why don't you track hours?" }, { "@type": "Question", "acceptedAnswer": { "@type": "Answer", "text": "We work with operators, not lottery winners. If a request would require breaking physics, the law, or a third party's systems, we say so, and if we can't align, we walk. The guarantee is mutual: you can fire us any week; we can also fire ourselves." }, "name": "What does 'expectations detached from reality' mean?" }, { "@type": "Question", "acceptedAnswer": { "@type": "Answer", "text": "We weigh four things: maturity of the surrounding ecosystem (libraries, hiring market, debugging tools), seriousness of the worst failure mode, presence of an exit path back to a mature stack, and whether the competitive advantage is real or vanity. If three of four don't pass, we recommend the conventional stack." }, "name": "How do you decide whether a bleeding-edge tech is production-ready?" }, { "@type": "Question", "acceptedAnswer": { "@type": "Answer", "text": "We'll tell you up front and structure the engagement around it: smaller initial scope, parallel safer fallback path, explicit budget for upstream contributions and unexpected work. Alpha-stage tech ships, but only when you scope it like research, not like a delivery commitment." }, "name": "What if the tech we want is still in alpha?" }, { "@type": "Question", "acceptedAnswer": { "@type": "Answer", "text": "Both. R&D engagements are scoped as time-boxed exploration with deliverables (working prototype + written assessment + recommendation). Production engagements have a hard delivery commitment. We don't pretend an R&D engagement is production work. That's how teams burn budget for two quarters with nothing to show." }, "name": "Do you take R&D engagements or only production work?" }, { "@type": "Question", "acceptedAnswer": { "@type": "Answer", "text": "You do. Standard work-for-hire terms transfer all IP to you on delivery, including R&D outputs. Any open-source contributions we make upstream during the project (often necessary to make alpha tech work) are clearly listed in advance. We don't quietly ship your code to a public repo without disclosure." }, "name": "Who owns the IP from R&D outputs?" }, { "@type": "Question", "acceptedAnswer": { "@type": "Answer", "text": "Failed experiments are a budget line, not a surprise. For R&D-shaped engagements we typically reserve 20-30% of total budget for 'this didn't work, try something else.' If we hit a dead end fast (week one) we tell you and reroute. If we hit it late, the previous learnings still inform the production design we recommend. The worst outcome we plan for: you spend the R&D budget and we hand you a written 'do not build this' assessment with reasons. That's still a real deliverable." }, "name": "How do we budget for failed experiments on bleeding-edge tech?" } ], "speakable": { "@type": "SpeakableSpecification", "cssSelector": [ ".faq-question", ".faq-answer" ] } } ```