Web3 in Travel

Luca De Giglio

I don't understand things unless I do them. So I'm constantly building with blockchain and AI. I have over 40 projects running at the same time and each one of them teaches me something. In this podcast I share with you the most interesting learnings. If you wonder "How to apply AI in my travel business?" and are still uncertain about what blockchain is really for, I may help shed some light. 110 episodes since 2021. Season 2 starts now, and it leans hard into AI. For collaborations, advisory work or speaking: info@web3intravel.com and https://www.linkedin.com/in/luca-de-giglio/

  1. 1d ago

    Local AI

    Can a laptop do your company's AI work without sending a single byte outside? Luca De Giglio ran real travel-business tasks on a MacBook Pro with 48 GB of RAM, using the open-weight Qwen 3.8 27B model, and compared every answer with Claude Opus 5.5 through the API.On everyday tasks (reading a booking email, replying to a bad review, pricing a tour package) the local model matched Claude, at about a fifth of the speed and a fraction of the cost, and the data never left the laptop. On a 30-page supplier contract it still found the right cancellation charge, but in six minutes instead of sixteen seconds. On 600 bookings checked against a hotel invoice, it hit a wall.Then the questions that matter for a company: why more RAM is not enough, what actually fits on a laptop, why buying a machine is a bet, who maintains it, and where local AI makes sense in travel and hospitality.IN THIS EPISODE• Three light tests and two heavy tests: local vs. the Claude API.• Why a 64 GB server can be useless for AI, and a 48 GB Mac isn't.• The model as a book: capacity and bandwidth.• Ollama, LM Studio, and models tuned for one machine (DwarfStar, Sushi).• The money: 50× cheaper on electricity, and why that's rarely the point.• Maintenance, evals, and why private isn't automatically safe.• Guest data, contracts and margins: the travel use cases.CHAPTERS0:00 Intro0:20 Local AI: is it time to start?1:43 My laptop: 48 GB of RAM3:16 Why a big server is useless for AI4:08 Test 1: a booking email5:43 Test 2: reply to a bad review7:54 Test 3: a tour package margin9:22 Speed: tokens per second10:12 Cost, and where the data went11:25 Heavy test A: a 30-page contract14:05 Heavy test B: 600 bookings vs. an invoice16:43 Electricity: 50× cheaper17:25 The model is a book19:01 What runs on 48 GB, and the tools19:56 Models tuned for one machine22:29 Does local save you money?23:57 Buying a machine is a bet26:09 Finding the ceiling, and evals28:07 Maintenance28:53 Private isn't automatically safe29:32 Local AI in travel and hospitality30:57 A possible setup, and where to startFor collaborations, advisory work or speaking:info@web3intravel.comhttps://www.linkedin.com/in/luca-de-giglio/

  2. Oct 12

    Private AI

    Most companies are still asking how to use AI. The next question is how to use it privately. When your team plugs Claude or ChatGPT into the company's documents, where does that data go, and what can the AI labs do with it?In this episode of Web3 in Travel, Luca De Giglio explains why your data is worth far more to an AI lab than it ever was to Google, why a $20 subscription buys hundreds of dollars of inference, and what "we don't train on your data" really promises. He then walks through the options for private AI, from the most private to the least: local open-weight models on your own hardware, private APIs for open models, and Trusted Execution Environments (TEEs). For each, what it costs and what it actually protects.He closes with the strategy: route each task to the right model, decide which data must never leave the company, and accept that total privacy does not exist. You manage risk, you don't cancel it.IN THIS EPISODE• Why LLMs extract more value from your data than ads ever did.• The real economics of a $20 AI subscription.• Could an AI lab become a competitor in your industry?• Local models and open weights: DeepSeek, Kimi K3, Qwen, gpt-oss.• Private APIs and anonymized inference: what they cost, how private they are.• TEEs: hardware attestation, and why you still have to verify.• Routing: the right task to the right model.• The first step: decide which data never goes near an LLM.MENTIONED• Vitalik Buterin on a local model deciding what to send to frontier models: https://x.com/VitalikButerin/status/2106537633056969024CHAPTERS0:00 Intro0:20 The next question: how do I use AI privately?0:59 Google sold ads. LLMs take the value1:33 Your best insight, in the next model2:39 Why a $20 subscription is so cheap4:34 Do they train on your data?5:24 When the AI lab enters your industry7:51 Local models and open weights10:07 The cost of running AI yourself11:25 Private APIs: paying full price13:08 How private is anonymized?14:21 TEEs: trusted execution environments16:12 Routing: the right task to the right model17:43 A strategy for your data19:48 The first step: data that never leaves21:21 Nothing is 100% privateFor collaborations, advisory work or speaking:info@web3intravel.comhttps://www.linkedin.com/in/luca-de-giglio/

  3. Aug 25

    Season 2: Why This Podcast Is Now Also About AI

    Using AI, Luca De Giglio found an exotic bug in a Bitcoin wallet despite not being a Bitcoin developer—and the project’s developers accepted and merged the fix. That experience anchors the return of Web3 in Travel for a second season focused on what happens when AI becomes a practical building tool rather than a chat interface. Luca explains how he manages 40 active projects, runs most of his work on remote computers and experiments with local models, coding agents and multi-model verification. He also considers what these tools mean for development teams that either reject AI entirely or trust it without adequate checks. The discussion then connects AI with blockchain infrastructure: agents can create wallets, obtain funding and autonomously pay for API access using USDC and X402. For travel and technology leaders, the larger question is no longer simply whether AI can complete a task, but which consequential problems are now worth attempting—and how organizations should adapt their workflows, security practices and ambitions. CHAPTERS 0:00 Intro 0:20 Podcast Returns With AI 4:00 Forty Projects and Context Switching 6:40 Remote AI Coding Workflow 8:20 Local Models and AI Learning 12:00 AI Finds Crypto Wallet Bugs 17:40 Developers Resisting AI 19:40 Stripe Embraces AI and Blockchain 22:20 Agents Paying Through x402 IN THIS EPISODE • Why the podcast is returning with AI alongside its original blockchain and travel focus • The challenge of managing 40 projects while coding agents create constant context switching • How remote development keeps AI tasks running after the laptop is closed • Using Claude Code, Codex and Kimi to cross-check a suspected crypto software bug • Why both rejecting AI-generated code and trusting it uncritically create risks • How local models change the economics and pace of AI-assisted development • An example of an agent using a wallet, USDC and X402 to purchase API access — I don't understand things unless I do them, so I'm constantly building with blockchain and AI — over 40 projects at once. This podcast is where I share the most interesting learnings. For collaborations, advisory work or speaking: info@web3intravel.com https://www.linkedin.com/in/luca-de-giglio/

About

I don't understand things unless I do them. So I'm constantly building with blockchain and AI. I have over 40 projects running at the same time and each one of them teaches me something. In this podcast I share with you the most interesting learnings. If you wonder "How to apply AI in my travel business?" and are still uncertain about what blockchain is really for, I may help shed some light. 110 episodes since 2021. Season 2 starts now, and it leans hard into AI. For collaborations, advisory work or speaking: info@web3intravel.com and https://www.linkedin.com/in/luca-de-giglio/