1 00:00:00,000 --> 00:00:02,960 Welcome to the deep dive where we take complex stuff, 2 00:00:02,960 --> 00:00:05,120 break it down, and give you those key insights 3 00:00:05,120 --> 00:00:06,880 so you feel like you've really got a handle on it. 4 00:00:06,880 --> 00:00:09,200 So let's start with a problem 5 00:00:09,200 --> 00:00:12,360 pretty much everyone runs into, spreadsheets. 6 00:00:12,360 --> 00:00:14,680 You know, you kick off a project, track some inventory, 7 00:00:14,680 --> 00:00:16,880 maybe, because hey, it's easy, right, familiar. 8 00:00:16,880 --> 00:00:18,480 Right, super quick to get going. 9 00:00:18,480 --> 00:00:19,560 Exactly. 10 00:00:19,560 --> 00:00:22,200 But then maybe you hit a thousand rows, 11 00:00:22,200 --> 00:00:24,320 maybe more, and suddenly it crawls. 12 00:00:24,320 --> 00:00:28,200 Or you've got five people trying to edit the same file. 13 00:00:28,200 --> 00:00:29,040 Chaos. 14 00:00:29,040 --> 00:00:31,040 Yeah, and forget about building anything serious 15 00:00:31,040 --> 00:00:31,880 on top of it. 16 00:00:31,880 --> 00:00:34,040 No security, no real structure. 17 00:00:34,040 --> 00:00:35,360 You basically hit a wall. 18 00:00:35,360 --> 00:00:36,280 You've outgrown it. 19 00:00:36,280 --> 00:00:37,720 That's the spreadsheet disaster. 20 00:00:37,720 --> 00:00:40,320 That is the classic scalability crisis, yeah. 21 00:00:40,320 --> 00:00:42,880 You find yourself meeting, well, a proper database, 22 00:00:42,880 --> 00:00:44,800 something powerful, secure. 23 00:00:44,800 --> 00:00:46,680 But those are often, let's be honest, 24 00:00:46,680 --> 00:00:49,240 pretty intimidating, SQL, schemas. 25 00:00:49,240 --> 00:00:50,080 Yeah. 26 00:00:50,080 --> 00:00:52,040 It feels like you need an IT degree just to start. 27 00:00:52,040 --> 00:00:53,520 It's like this huge gap, isn't it, 28 00:00:53,520 --> 00:00:58,440 between simple and flexible and powerful, but complex. 29 00:00:58,440 --> 00:01:01,200 That gap is exactly what we're diving into today. 30 00:01:01,200 --> 00:01:03,540 Now, before we get into the tool that's trying to bridge it, 31 00:01:03,540 --> 00:01:05,800 a quick word about our supporter for this deep dive, 32 00:01:05,800 --> 00:01:06,800 Safe Server. 33 00:01:06,800 --> 00:01:07,840 Ah, yes. 34 00:01:07,840 --> 00:01:08,800 Because if you're looking at tools 35 00:01:08,800 --> 00:01:10,220 like the one we're discussing, 36 00:01:10,220 --> 00:01:12,200 tools that give you serious control, 37 00:01:12,200 --> 00:01:13,480 maybe even self-hosting, 38 00:01:13,480 --> 00:01:15,480 with things like Docker and Postgres. 39 00:01:15,480 --> 00:01:17,640 Well, Safe Server is all about providing 40 00:01:17,640 --> 00:01:20,200 the solid infrastructure for that kind of setup. 41 00:01:20,200 --> 00:01:21,640 Helping you manage that power. 42 00:01:21,640 --> 00:01:22,560 Exactly. 43 00:01:22,560 --> 00:01:24,200 Supporting your digital transformation, 44 00:01:24,200 --> 00:01:25,740 giving you control. 45 00:01:25,740 --> 00:01:30,140 You can find out more at www.safe-server.de. 46 00:01:30,140 --> 00:01:32,640 Okay, so our mission today, 47 00:01:32,640 --> 00:01:34,560 we're taking a deep dive into Teeble. 48 00:01:34,560 --> 00:01:38,520 The tagline is the next-gen Airtable alternative. 49 00:01:38,520 --> 00:01:40,120 No code Postgres. 50 00:01:40,120 --> 00:01:40,960 Quite a claim. 51 00:01:40,960 --> 00:01:41,800 It is. 52 00:01:41,800 --> 00:01:43,280 We need to figure out how they stick 53 00:01:43,280 --> 00:01:45,880 a user-friendly spreadsheet-like face 54 00:01:45,880 --> 00:01:49,360 onto, well, a serious database engine like Postgres. 55 00:01:49,360 --> 00:01:51,880 And crucially, how does it avoid the usual traps 56 00:01:51,880 --> 00:01:54,960 of no-code tools where you eventually hit limitations? 57 00:01:54,960 --> 00:01:55,460 Right. 58 00:01:55,460 --> 00:01:57,720 How do they make that power genuinely accessible? 59 00:01:57,720 --> 00:01:58,600 Let's unpack it. 60 00:01:58,600 --> 00:02:00,320 Starting with the basics, what is Teeble? 61 00:02:00,320 --> 00:02:01,040 Simply put. 62 00:02:01,040 --> 00:02:01,540 OK. 63 00:02:01,540 --> 00:02:04,880 Fundamentally, it's built as an AI-driven no-code database. 64 00:02:04,880 --> 00:02:06,960 The idea is that anyone can use it to build 65 00:02:06,960 --> 00:02:08,240 a pretty powerful application. 66 00:02:08,240 --> 00:02:09,080 That's ambitious. 67 00:02:09,080 --> 00:02:10,120 Well, that's the goal. 68 00:02:10,120 --> 00:02:13,880 It's designed to take messy data, stuff sitting in documents 69 00:02:13,880 --> 00:02:17,040 or chaotic spreadsheets, and quickly give it structure, 70 00:02:17,040 --> 00:02:18,760 turn it into a working app. 71 00:02:18,760 --> 00:02:19,400 Fast. 72 00:02:19,400 --> 00:02:21,600 And the key for that accessibility, I guess, 73 00:02:21,600 --> 00:02:22,920 is the interface. 74 00:02:22,920 --> 00:02:24,080 It looks like a spreadsheet. 75 00:02:24,080 --> 00:02:24,680 Exactly. 76 00:02:24,680 --> 00:02:25,720 That's the hook. 77 00:02:25,720 --> 00:02:27,840 If you know how to use Excel or Google Sheets, 78 00:02:27,840 --> 00:02:30,080 you look at T-Bill and you think, OK, I get this. 79 00:02:30,080 --> 00:02:31,760 It uses that familiar grid. 80 00:02:31,760 --> 00:02:34,240 That immediately lowers the barrier, doesn't it? 81 00:02:34,240 --> 00:02:36,720 No steep learning curve right off the bat. 82 00:02:36,720 --> 00:02:37,320 Precisely. 83 00:02:37,320 --> 00:02:39,560 And it's built for real-time collaboration, 84 00:02:39,560 --> 00:02:41,960 like a Google Doc, but for structured data, 85 00:02:41,960 --> 00:02:43,440 multiple people working together. 86 00:02:43,440 --> 00:02:45,680 So it feels simple, but what about the features? 87 00:02:45,680 --> 00:02:47,200 Is it just a basic grid? 88 00:02:47,200 --> 00:02:48,160 Oh, no, it's packed. 89 00:02:48,160 --> 00:02:50,240 They've included all the stuff you'd actually need. 90 00:02:50,240 --> 00:02:52,720 Formula support is there, which is critical. 91 00:02:52,720 --> 00:02:56,680 You can add custom columns, do batch edits, 92 00:02:56,680 --> 00:03:00,120 convert field types under Derridao, proper history 93 00:03:00,120 --> 00:03:03,000 tracking, comments for collaboration, 94 00:03:03,000 --> 00:03:05,520 plus importing and exporting data easily. 95 00:03:05,520 --> 00:03:08,640 OK, sounds like standard table stakes, but good to have. 96 00:03:08,640 --> 00:03:10,240 What about working with the data? 97 00:03:10,240 --> 00:03:12,280 Yeah, that's where it gets more powerful. 98 00:03:12,280 --> 00:03:15,800 Strong validation rules, filtering, grouping, sorting, 99 00:03:15,800 --> 00:03:19,560 aggregation, all the tools you need to actually analyze 100 00:03:19,560 --> 00:03:22,520 and manage potentially large amounts of data, 101 00:03:22,520 --> 00:03:24,600 right there in that familiar interface. 102 00:03:24,600 --> 00:03:26,240 So it's trying to hide the complexity 103 00:03:26,240 --> 00:03:27,440 behind that friendly face. 104 00:03:27,440 --> 00:03:29,840 That seems to be the core design philosophy. 105 00:03:29,840 --> 00:03:33,000 Make it approachable, but don't skimp on the power tools. 106 00:03:33,000 --> 00:03:35,760 But a spreadsheet view is just one way to look at data. 107 00:03:35,760 --> 00:03:37,160 What else does it offer? 108 00:03:37,160 --> 00:03:39,160 This is where a lot of simple tools fall down. 109 00:03:39,160 --> 00:03:41,920 Right, and this is where Table starts feeling more 110 00:03:41,920 --> 00:03:43,240 like an application builder. 111 00:03:43,240 --> 00:03:44,480 It offers multiple views. 112 00:03:44,480 --> 00:03:45,640 You're not stuck in the grid. 113 00:03:45,640 --> 00:03:46,560 OK, like what? 114 00:03:46,560 --> 00:03:49,040 Well, you've got the standard grid view, obviously. 115 00:03:49,040 --> 00:03:50,880 Then there's a form view, which is 116 00:03:50,880 --> 00:03:52,880 great for just entering data cleanly. 117 00:03:52,880 --> 00:03:55,440 Think surveys or sign up forms. 118 00:03:55,440 --> 00:03:56,320 Makes sense. 119 00:03:56,320 --> 00:03:59,280 Then a can-been view, like Trello boards. 120 00:03:59,280 --> 00:04:03,400 Perfect for managing workflows, tasks, sales pipelines, 121 00:04:03,400 --> 00:04:04,960 moving things through stages. 122 00:04:04,960 --> 00:04:07,800 Ah, OK, so you can visualize processes. 123 00:04:07,800 --> 00:04:08,720 That's useful. 124 00:04:08,720 --> 00:04:09,520 Definitely. 125 00:04:09,520 --> 00:04:12,040 There's also a gallery view, better for visual stuff, 126 00:04:12,040 --> 00:04:15,240 maybe product catalogs or image assets, 127 00:04:15,240 --> 00:04:18,960 and a calendar view for anything database, like scheduling. 128 00:04:18,960 --> 00:04:21,680 So the same underlying data can be viewed in completely 129 00:04:21,680 --> 00:04:23,240 different ways depending on the task. 130 00:04:23,240 --> 00:04:24,280 Exactly. 131 00:04:24,280 --> 00:04:26,920 The data itself is separate from how you look at it. 132 00:04:26,920 --> 00:04:29,280 That flexibility is pretty key for building something 133 00:04:29,280 --> 00:04:30,840 beyond just a simple list. 134 00:04:30,840 --> 00:04:34,580 OK, so the front end looks approachable, flexible, 135 00:04:34,580 --> 00:04:37,920 feature-rich for non-tech users. 136 00:04:37,920 --> 00:04:40,920 But you mentioned Postgres in the tagline. 137 00:04:40,920 --> 00:04:43,200 That sounds serious. 138 00:04:43,200 --> 00:04:45,840 It is, and that's the core differentiator, really, 139 00:04:45,840 --> 00:04:47,440 the no-code Postgres part. 140 00:04:47,440 --> 00:04:49,360 What does that actually mean for the user? 141 00:04:49,360 --> 00:04:51,880 It means that when you create a table in Table's simple 142 00:04:51,880 --> 00:04:54,640 interface, you are directly creating a real table 143 00:04:54,640 --> 00:04:57,480 on a physical Postgres database behind the scenes. 144 00:04:57,480 --> 00:05:00,160 Ah, so it's not some proprietary, lightweight 145 00:05:00,160 --> 00:05:01,480 database they built themselves. 146 00:05:01,480 --> 00:05:01,980 Nope. 147 00:05:01,980 --> 00:05:04,720 They're leveraging a mature, powerful, enterprise-grade 148 00:05:04,720 --> 00:05:05,920 database engine. 149 00:05:05,920 --> 00:05:09,000 Postgres is known for handling huge amounts of data reliably. 150 00:05:09,000 --> 00:05:11,120 And that's the key to the scalability claim, 151 00:05:11,120 --> 00:05:12,820 managing millions of rows. 152 00:05:12,820 --> 00:05:13,880 That's the promise. 153 00:05:13,880 --> 00:05:16,800 Because it's built on Postgres, it inherits that power. 154 00:05:16,800 --> 00:05:18,720 They talk about seconds to react, 155 00:05:18,720 --> 00:05:22,480 even with massive data sets, like a million rows or more. 156 00:05:22,480 --> 00:05:25,080 Which is where many other no-code tools start to choke. 157 00:05:25,080 --> 00:05:26,080 Exactly. 158 00:05:26,080 --> 00:05:30,000 Those platforms often falter at such scales, as they put it. 159 00:05:30,000 --> 00:05:33,600 No business wants to build their core operations on a tool, 160 00:05:33,600 --> 00:05:36,560 only to be told they'll outgrow it once they hit, say, 161 00:05:36,560 --> 00:05:38,920 100,000 orders or customers. 162 00:05:38,920 --> 00:05:40,440 Right, that's a nightmare scenario. 163 00:05:40,440 --> 00:05:42,800 You're locked in, and performance stinks. 164 00:05:42,800 --> 00:05:44,940 Teeble aims to avoid that completely. 165 00:05:44,940 --> 00:05:47,560 It's designed to grow with you, handling lots of data 166 00:05:47,560 --> 00:05:48,880 from day one. 167 00:05:48,880 --> 00:05:51,320 Right now, it supports Squealite for development, 168 00:05:51,320 --> 00:05:53,680 which is easy, and Postgres for production. 169 00:05:53,680 --> 00:05:56,460 So using Postgres isn't just about speed, is it? 170 00:05:56,460 --> 00:05:58,200 It implies reliability, too. 171 00:05:58,200 --> 00:05:58,720 Absolutely. 172 00:05:58,720 --> 00:06:00,120 It's about data integrity. 173 00:06:00,120 --> 00:06:02,960 Postgres is robust, transactional. 174 00:06:02,960 --> 00:06:05,720 Your data is safer, managed more professionally 175 00:06:05,720 --> 00:06:09,480 than in, say, a spreadsheet or a less-matured database system. 176 00:06:09,480 --> 00:06:12,880 It gives even small teams that enterprise level of data safety. 177 00:06:12,880 --> 00:06:17,840 OK, but Postgres isn't exactly known for being click and play. 178 00:06:17,840 --> 00:06:20,820 How do they bridge that gap for developers? 179 00:06:20,820 --> 00:06:23,180 It sounds like they're trying to appeal to tech users, too. 180 00:06:23,180 --> 00:06:23,960 They are. 181 00:06:23,960 --> 00:06:26,080 It's quite unusual for a no-code tool. 182 00:06:26,080 --> 00:06:28,500 They seem to understand that, eventually, businesses 183 00:06:28,500 --> 00:06:31,080 need deeper integration or customization. 184 00:06:31,080 --> 00:06:33,320 So how do developers interact with it? 185 00:06:33,320 --> 00:06:36,120 They offer direct SQL query access. 186 00:06:36,120 --> 00:06:39,120 So if you know SQL, you can query the underlying Postgres 187 00:06:39,120 --> 00:06:40,160 database directly. 188 00:06:40,160 --> 00:06:40,660 Wow. 189 00:06:40,660 --> 00:06:41,840 OK. 190 00:06:41,840 --> 00:06:42,740 That opens things up. 191 00:06:42,740 --> 00:06:45,840 Yeah, and they provide an SDK, a software development 192 00:06:45,840 --> 00:06:48,560 kit, which lets developers build extensions, plugins, 193 00:06:48,560 --> 00:06:49,560 custom logic. 194 00:06:49,560 --> 00:06:52,080 So if the no-code interface isn't enough, 195 00:06:52,080 --> 00:06:54,140 you can bring in developers to build on top. 196 00:06:54,140 --> 00:06:54,920 Precisely. 197 00:06:54,920 --> 00:06:57,360 The idea is you don't hit a hard ceiling. 198 00:06:57,360 --> 00:06:59,560 The non-tech users stay in the friendly interface, 199 00:06:59,560 --> 00:07:02,600 but developers aren't locked out when more advanced needs arise. 200 00:07:02,600 --> 00:07:04,600 They can work with it like a standard database. 201 00:07:04,600 --> 00:07:05,640 But hang on. 202 00:07:05,640 --> 00:07:08,680 Giving SQL access, isn't that risky? 203 00:07:08,680 --> 00:07:11,480 Could a beginner accidentally break things using the simple UI 204 00:07:11,480 --> 00:07:13,520 if there's raw SQL access somewhere? 205 00:07:13,520 --> 00:07:14,320 That's a good point. 206 00:07:14,320 --> 00:07:18,480 It comes down to permissions and roles, presumably. 207 00:07:18,480 --> 00:07:21,720 The direct SQL access and SDK would 208 00:07:21,720 --> 00:07:25,400 be for specific developer roles, not your average user 209 00:07:25,400 --> 00:07:26,920 clicking around the grid view. 210 00:07:26,920 --> 00:07:28,440 OK, so there are guardrails. 211 00:07:28,440 --> 00:07:31,960 Yeah, the interface acts as the guardrail for the typical user. 212 00:07:31,960 --> 00:07:34,560 The advanced tools are there for those who need them, 213 00:07:34,560 --> 00:07:36,600 likely with stricter access controls. 214 00:07:36,600 --> 00:07:38,440 It's about accommodating the whole life 215 00:07:38,440 --> 00:07:40,320 cycle of a growing application. 216 00:07:40,320 --> 00:07:42,720 And this openness extends to how you deploy it, right? 217 00:07:42,720 --> 00:07:43,520 The licensing. 218 00:07:43,520 --> 00:07:45,120 Yes, and this is really important. 219 00:07:45,120 --> 00:07:47,920 The Community Edition is free and open source 220 00:07:47,920 --> 00:07:49,520 under the AGPL license. 221 00:07:49,520 --> 00:07:50,640 AGPL. 222 00:07:50,640 --> 00:07:53,480 That's one of the strong copyleft licenses, isn't it? 223 00:07:53,480 --> 00:07:55,720 Ensures derivative work stay open. 224 00:07:55,720 --> 00:07:56,560 It is. 225 00:07:56,560 --> 00:07:58,480 But the key takeaway for most users 226 00:07:58,480 --> 00:07:59,800 is the freedom it gives you. 227 00:07:59,800 --> 00:08:03,200 You can self-host it, put it on your own servers using Docker, 228 00:08:03,200 --> 00:08:06,200 or use one of those one-click deployment platforms. 229 00:08:06,200 --> 00:08:07,380 So no vendor lock-in. 230 00:08:07,380 --> 00:08:07,880 Exactly. 231 00:08:07,880 --> 00:08:10,640 That's a huge fear with proprietary cloud platforms. 232 00:08:10,640 --> 00:08:13,080 With Tipple's Community Edition, you own the instance. 233 00:08:13,080 --> 00:08:14,320 You control the data. 234 00:08:14,320 --> 00:08:17,440 You're not trapped if pricing changes or the company pivots. 235 00:08:17,440 --> 00:08:20,040 That freedom is massive for long-term planning. 236 00:08:20,040 --> 00:08:22,940 That really tackles what some call the no-code paradox. 237 00:08:22,940 --> 00:08:25,520 The easier it is, the less control you have. 238 00:08:25,520 --> 00:08:27,520 Tipple sees you saying you can have both. 239 00:08:27,520 --> 00:08:28,320 That's the goal. 240 00:08:28,320 --> 00:08:31,560 Ease of use without sacrificing control or scalability. 241 00:08:31,560 --> 00:08:33,600 Which brings us to data control and privacy. 242 00:08:33,600 --> 00:08:36,680 If I'm not self-hosting, where does my data live? 243 00:08:36,680 --> 00:08:37,840 How secure is it? 244 00:08:37,840 --> 00:08:39,880 Especially using that enterprise backbone. 245 00:08:39,880 --> 00:08:42,760 Crucial question, especially with sensitive data. 246 00:08:42,760 --> 00:08:45,840 Most no-code tools are cloud only. 247 00:08:45,840 --> 00:08:47,800 Your data sits on their servers. 248 00:08:47,800 --> 00:08:51,000 Which means you're dependent on them for uptime, security, 249 00:08:51,000 --> 00:08:51,680 everything. 250 00:08:51,680 --> 00:08:53,520 And switching is painful. 251 00:08:53,520 --> 00:08:54,600 It's really painful. 252 00:08:54,600 --> 00:08:56,320 Tipple offers the choice. 253 00:08:56,320 --> 00:08:58,400 You can use their cloud service, sure. 254 00:08:58,400 --> 00:09:00,840 But you can also deploy it on premise, 255 00:09:00,840 --> 00:09:03,720 on your own infrastructure, or even run it locally if needed. 256 00:09:03,720 --> 00:09:04,880 Choice is key. 257 00:09:04,880 --> 00:09:06,080 And they have certifications. 258 00:09:06,080 --> 00:09:10,320 Yeah, they mentioned ISO 9301 and ISO 2701. 259 00:09:10,320 --> 00:09:12,800 Basically, certifications for quality management and 260 00:09:12,800 --> 00:09:14,680 information security standards. 261 00:09:14,680 --> 00:09:16,800 It signals a commitment to doing things properly, 262 00:09:16,800 --> 00:09:19,200 reducing risk for businesses using their platform. 263 00:09:19,200 --> 00:09:21,560 So private deployment means full data sovereignty. 264 00:09:21,560 --> 00:09:23,800 You control where it is, who accesses it. 265 00:09:23,800 --> 00:09:27,800 Right, blending that no code ease with serious enterprise 266 00:09:27,800 --> 00:09:29,160 security controls. 267 00:09:29,160 --> 00:09:32,800 OK, now for the really buzzy part, AI. 268 00:09:32,800 --> 00:09:35,840 It sounds like it's baked in deep, not just tacked on. 269 00:09:35,840 --> 00:09:38,280 They call Teeble the database agent. 270 00:09:38,280 --> 00:09:39,120 What does that mean? 271 00:09:39,120 --> 00:09:41,920 It suggests AI is fundamental to how it operates, 272 00:09:41,920 --> 00:09:44,520 moving beyond just a database UI into something 273 00:09:44,520 --> 00:09:45,560 that builds for you. 274 00:09:45,560 --> 00:09:46,240 How so? 275 00:09:46,240 --> 00:09:48,160 Like generating things automatically? 276 00:09:48,160 --> 00:09:50,080 Yeah, the vision is quite ambitious. 277 00:09:50,080 --> 00:09:53,040 They say you can use a single prompt, just type what you need, 278 00:09:53,040 --> 00:09:55,440 and it can generate the live database, the application 279 00:09:55,440 --> 00:09:57,680 interface, and even the automations to go with it. 280 00:09:57,680 --> 00:09:58,240 Whoa. 281 00:09:58,240 --> 00:09:59,280 Can you give an example? 282 00:09:59,280 --> 00:10:00,000 What would that look like? 283 00:10:00,000 --> 00:10:01,780 OK, imagine you run a small bakery. 284 00:10:01,780 --> 00:10:04,320 You could prompt something like, create an order tracking 285 00:10:04,320 --> 00:10:07,360 system with customer details, order items, delivery dates, 286 00:10:07,360 --> 00:10:10,000 and a Kanban view showing order status 287 00:10:10,000 --> 00:10:12,040 from received to delivered. 288 00:10:12,040 --> 00:10:14,320 And Teeble just builds that. 289 00:10:14,320 --> 00:10:17,160 As the database agent, the idea is it interprets that, 290 00:10:17,160 --> 00:10:19,800 designs the database tables, customer table, order table, 291 00:10:19,800 --> 00:10:23,280 et cetera, sets up the fields, creates the Kanban view, 292 00:10:23,280 --> 00:10:26,840 and maybe even basic automations for moving orders along. 293 00:10:26,840 --> 00:10:29,040 It turns your request into a functional app. 294 00:10:29,040 --> 00:10:31,640 That's potentially a massive time saver. 295 00:10:31,640 --> 00:10:34,360 A huge leap in making complex setups accessible. 296 00:10:34,360 --> 00:10:36,960 It really lowers the barrier to creating 297 00:10:36,960 --> 00:10:38,440 structured applications. 298 00:10:38,440 --> 00:10:42,920 But AI models, they mentioned supporting DeepSeek, OpenAI, 299 00:10:42,920 --> 00:10:45,640 Claude, and even self-hosted models. 300 00:10:45,640 --> 00:10:47,800 If I'm self-hosting Teeble, does 301 00:10:47,800 --> 00:10:50,600 managing those AI models become my problem? 302 00:10:50,600 --> 00:10:52,160 Is that complex? 303 00:10:52,160 --> 00:10:55,440 Well, self-hosting any large language model, LLM, 304 00:10:55,440 --> 00:10:57,520 involves technical setup, definitely. 305 00:10:57,520 --> 00:10:59,680 But Teeble's approach seems to be about providing 306 00:10:59,680 --> 00:11:00,880 the integration points. 307 00:11:00,880 --> 00:11:02,040 This is flexible? 308 00:11:02,040 --> 00:11:02,640 It seems so. 309 00:11:02,640 --> 00:11:05,360 It's designed with API compatibility in mind. 310 00:11:05,360 --> 00:11:07,000 You can plug in your preferred model, 311 00:11:07,000 --> 00:11:08,760 whether it's a commercial one via API 312 00:11:08,760 --> 00:11:11,560 or when you run privately for maximum data control. 313 00:11:11,560 --> 00:11:14,760 Again, avoiding lock-in, even with the AI component. 314 00:11:14,760 --> 00:11:16,680 So you choose your AI, you choose your hosting, 315 00:11:16,680 --> 00:11:18,800 it keeps coming back to flexibility and control. 316 00:11:18,800 --> 00:11:20,640 That seems to be the recurring theme, yes. 317 00:11:20,640 --> 00:11:23,000 And what about really large organizations 318 00:11:23,000 --> 00:11:24,360 with complex security needs? 319 00:11:24,360 --> 00:11:25,480 Is there something more? 320 00:11:25,480 --> 00:11:27,600 That's where the Enterprise Edition comes in. 321 00:11:27,600 --> 00:11:30,360 It adds features specifically for larger deployments, 322 00:11:30,360 --> 00:11:32,920 things like advanced admin controls, audit logs, 323 00:11:32,920 --> 00:11:34,960 and something they call the authority matrix. 324 00:11:34,960 --> 00:11:38,080 Authority matrix, sounds serious. 325 00:11:38,080 --> 00:11:41,320 It implies very granular permission controls, 326 00:11:41,320 --> 00:11:44,900 managing exactly who can see and edit what data 327 00:11:44,900 --> 00:11:47,360 down to specific roles or fields, 328 00:11:47,360 --> 00:11:49,940 essential for compliance in regulated industries 329 00:11:49,940 --> 00:11:51,520 like finance or healthcare. 330 00:11:51,520 --> 00:11:53,920 It ensures the platform scales not just in data volume, 331 00:11:53,920 --> 00:11:55,800 but also in governance complexity. 332 00:11:55,800 --> 00:11:57,400 Okay, let's try and wrap this up. 333 00:11:57,400 --> 00:12:00,320 What we've seen is T-Bull attempting to square a circle. 334 00:12:00,320 --> 00:12:02,040 It starts with this really simple, 335 00:12:02,040 --> 00:12:05,080 familiar spreadsheet interface, easy entry point. 336 00:12:05,080 --> 00:12:06,440 Right, very accessible. 337 00:12:06,440 --> 00:12:08,720 But underneath, it's powered by Postgres, 338 00:12:08,720 --> 00:12:11,800 giving it serious scalability for millions of rows 339 00:12:11,800 --> 00:12:13,720 and enterprise-grade reliability. 340 00:12:13,720 --> 00:12:16,480 Avoiding the usual no-code performance ceiling. 341 00:12:16,480 --> 00:12:18,120 Plus, it offers genuine freedom 342 00:12:18,120 --> 00:12:19,920 through its open-source community edition 343 00:12:19,920 --> 00:12:23,240 and self-hosting options, tackling vendor lock-in head-on. 344 00:12:23,240 --> 00:12:25,440 Control over your data and deployment. 345 00:12:25,440 --> 00:12:28,460 And then it layers on this ambitious AI integration, 346 00:12:28,460 --> 00:12:31,440 acting as a database agent to potentially build apps 347 00:12:31,440 --> 00:12:32,680 from simple prompts, 348 00:12:32,680 --> 00:12:34,600 while still letting you choose your AI model. 349 00:12:34,600 --> 00:12:36,240 It's a pretty compelling package, 350 00:12:36,240 --> 00:12:39,920 aiming to serve everyone from a single-user ditching Excel 351 00:12:39,920 --> 00:12:44,440 to a large enterprise needing custom, secure applications. 352 00:12:44,440 --> 00:12:46,340 It really does seem to offer that blend 353 00:12:46,340 --> 00:12:48,640 of ease, power, and control. 354 00:12:48,640 --> 00:12:51,400 Flexibility seems to be the watchword. 355 00:12:51,400 --> 00:12:53,020 So it leaves us with a final thought 356 00:12:53,020 --> 00:12:54,720 for you, the listener, to chew on. 357 00:12:54,720 --> 00:12:57,760 If tools like Table make it possible 358 00:12:57,760 --> 00:13:00,000 for almost anyone to build high-performance, 359 00:13:00,000 --> 00:13:03,080 scalable applications, and maintain full control 360 00:13:03,080 --> 00:13:05,020 over their data through self-hosting. 361 00:13:05,020 --> 00:13:08,560 What does that mean for the role 362 00:13:08,560 --> 00:13:10,800 of the traditional software developer and businesses? 363 00:13:10,800 --> 00:13:13,520 Yeah, does their role shift more towards being, 364 00:13:13,520 --> 00:13:15,320 I don't know, architects, integrators, 365 00:13:15,320 --> 00:13:17,200 curators of these powerful building blocks, 366 00:13:17,200 --> 00:13:19,880 rather than just writing every line of code from scratch? 367 00:13:19,880 --> 00:13:21,960 Something to think about as these no-code 368 00:13:21,960 --> 00:13:24,460 and low-code platforms get even more powerful. 369 00:13:24,460 --> 00:13:26,360 A fascinating question for the future. 370 00:13:26,360 --> 00:13:28,960 And remember, our exploration of Table today 371 00:13:28,960 --> 00:13:30,920 was supported by SafeServer. 372 00:13:30,920 --> 00:13:32,600 If you're considering self-hosting 373 00:13:32,600 --> 00:13:34,720 powerful open-source tools like this, 374 00:13:34,720 --> 00:13:37,680 SafeServer focuses on providing the robust infrastructure 375 00:13:37,680 --> 00:13:40,280 you need for that digital transformation journey. 376 00:13:40,280 --> 00:13:43,800 Check them out at www.safeserver.de. 377 00:13:43,800 --> 00:13:45,280 Thanks for joining us on the deep dive. 378 00:13:45,280 --> 00:13:46,520 We'll catch you next time.