[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"site-settings":3,"blog-post:laravel-database-transactions":8,"blog-posts-latest:24":31,"site-content":324,"blog-comments:6bbe0ad8-0c6d-4172-b279-ded8e2ca9416":541},{"id":4,"accent_theme":5,"font_theme":6,"updated_at":7},1,"midnight","saas","2026-10-28T07:05:59.308034+00:00",{"id":9,"title":10,"slug":11,"excerpt":12,"content":13,"cover_image":14,"meta_title":15,"meta_description":16,"og_image":17,"tags":18,"status":24,"published_at":25,"view_count":26,"deleted_at":27,"deleted_reason":28,"created_at":29,"updated_at":30},"6bbe0ad8-0c6d-4172-b279-ded8e2ca9416","Laravel Database Transactions: When and Why to Use DB::transaction()","laravel-database-transactions","DB::transaction() runs a closure inside a SQL transaction: Laravel commits if it finishes, and rolls back if it throws. Use it when one action writes more than one row and a half-finished write would leave bad data.","\u003Ch2 id=\"quick-answer\">Quick Answer\u003C\u002Fh2>\n\u003Cp>DB::transaction() runs a closure inside a database transaction: Laravel commits if the closure finishes, and rolls back if it throws. Use it when one user action writes more than one row or table and a half-finished write would leave bad data — transfers, orders plus stock, user plus profile. Skip it for a single update, for reads, and for anything that talks to the network.\u003C\u002Fp>\n\n\u003Ch2 id=\"quick-facts\">Quick Facts\u003C\u002Fh2>\n\u003Ctable>\n\u003Cthead>\u003Ctr>\u003Cth>Item\u003C\u002Fth>\u003Cth>Details\u003C\u002Fth>\u003C\u002Ftr>\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\u003Ctd>Topic\u003C\u002Ftd>\u003Ctd>Laravel database transactions\u003C\u002Ftd>\u003C\u002Ftr>\n\u003Ctr>\u003Ctd>Category\u003C\u002Ftd>\u003Ctd>Laravel \u002F PHP \u002F Backend\u003C\u002Ftd>\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\n\u003Cnav class=\"blog-toc\" aria-label=\"Table of contents\">\n\u003Ch2 id=\"table-of-contents\">Table of Contents\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Ca href=\"#what-is-laravel-database-transactions\">What Is Laravel Database Transactions?\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"#why-it-matters\">Why It Matters\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"#how-it-works\">How It Works\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"#step-by-step-guide\">Step-by-Step Guide\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"#real-world-example\">Real-World Example\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"#pros-cons\">Pros &amp; Cons\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"#best-practices\">Best Practices\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"#common-mistakes\">Common Mistakes\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"#frequently-asked-questions\">FAQs\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"#key-takeaways\">Key Takeaways\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fnav>\n\n\u003Ch2 id=\"what-is-laravel-database-transactions\">What Is Laravel Database Transactions?\u003C\u002Fh2>\n\u003Cp>A transaction is the database saying: treat these queries as one unit. All of them land, or none of them do. \u003Ccode>DB::transaction()\u003C\u002Fcode> is Laravel’s wrapper around \u003Ccode>BEGIN\u003C\u002Fcode> \u002F \u003Ccode>COMMIT\u003C\u002Fcode> \u002F \u003Ccode>ROLLBACK\u003C\u002Fcode> — not a queue, not a cache, not a lock by itself.\u003C\u002Fp>\n\u003Cp>Eloquent \u003Ccode>save()\u003C\u002Fcode> on one model is already a single statement. You do not wrap that for “safety.” You wrap the stretch where two writes must stay in sync. If MySQL is on MyISAM, this API still runs and does almost nothing useful. InnoDB (or Postgres) is the actual requirement.\u003C\u002Fp>\n\n\u003Ch2 id=\"why-it-matters\">Why It Matters\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Half-finished writes are worse than a loud exception. An order row with no stock decrement, or a debit with no credit, sits in production until a human notices.\u003C\u002Fli>\n\u003Cli>The closure form beats hand-rolled \u003Ccode>beginTransaction()\u003C\u002Fcode> because an uncaught exception rolls back for you. You still have to let it bubble.\u003C\u002Fli>\n\u003Cli>Pass an attempts count and Laravel retries deadlocks. Checkout and wallet code hits that under load; a single try just 500s the user.\u003C\u002Fli>\n\u003C\u002Ful>\n\n\u003Ch2 id=\"how-it-works\">How It Works\u003C\u002Fh2>\n\u003Cp>Nothing magic in PHP here. The query grammar talks to the connection; the database engine enforces atomicity.\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cstrong>BEGIN\u003C\u002Fstrong> — Laravel opens a transaction on the connection the closure will use.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Work\u003C\u002Fstrong> — Your queries run. Rows you \u003Ccode>lockForUpdate()\u003C\u002Fcode> stay locked until the end. Other requests wait or deadlock.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>COMMIT or ROLLBACK\u003C\u002Fstrong> — Clean return commits. Any throwable rolls back, then Laravel rethrows. Nested \u003Ccode>DB::transaction()\u003C\u002Fcode> calls use savepoints, not a second real transaction. The outer commit is the one that makes data visible.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>Side effects are not the database. A queued job, a mail, a HTTP call inside the closure still happens even if you later roll back — unless you defer them with \u003Ccode>DB::afterCommit()\u003C\u002Fcode> or \u003Ccode>$afterCommit = true\u003C\u002Fcode> on the job.\u003C\u002Fp>\n\n\u003Ch2 id=\"step-by-step-guide\">Step-by-Step Guide\u003C\u002Fh2>\n\u003Ch3 id=\"step-1\">Step 1: Spot the multi-write\u003C\u002Fh3>\n\u003Cp>Read the action, not the class name. If success means “row A and row B both change,” it belongs in a transaction. Transfer, place order, register user + profile, refund + restock. One \u003Ccode>Model::query()-&gt;update()\u003C\u002Fcode> is not that list.\u003C\u002Fp>\n\u003Cp>If the second write can fail (unique constraint, check, insufficient stock) and you would not want the first write to stay, wrap both.\u003C\u002Fp>\n\n\u003Ch3 id=\"step-2\">Step 2: Wrap the writes\u003C\u002Fh3>\n\u003Cp>Import the facade and put only database work in the closure. Throw on business failure so Laravel rolls back — a \u003Ccode>false\u003C\u002Fcode> return still commits.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>use Illuminate\\Support\\Facades\\DB;\n\nDB::transaction(function () use ($fromId, $toId, $amount) {\n    $from = Account::whereKey($fromId)-&gt;lockForUpdate()-&gt;firstOrFail();\n    $to = Account::whereKey($toId)-&gt;lockForUpdate()-&gt;firstOrFail();\n\n    if ($from-&gt;balance &lt; $amount) {\n        throw new \\RuntimeException('Insufficient funds');\n    }\n\n    $from-&gt;decrement('balance', $amount);\n    $to-&gt;increment('balance', $amount);\n}, 3);\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>The \u003Ccode>3\u003C\u002Fcode> is deadlock attempts. Done looks like this: both balances match, and a forced throw leaves both rows untouched. Check with a test or tinker: throw after the first decrement, then \u003Ccode>SELECT\u003C\u002Fcode> both accounts.\u003C\u002Fp>\n\n\u003Ch3 id=\"step-3\">Step 3: Move side effects after commit\u003C\u002Fh3>\n\u003Cp>Dispatch mail, jobs, and webhooks after the commit. If a worker runs mid-transaction it will miss the new row or see a ghost that then vanishes.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>DB::transaction(function () use ($order) {\n    $order-&gt;save();\n    $order-&gt;items()-&gt;saveMany($items);\n\n    DB::afterCommit(function () use ($order) {\n        ProcessOrder::dispatch($order-&gt;id);\n    });\n});\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Same idea on the job class: \u003Ccode>public bool $afterCommit = true;\u003C\u002Fcode> so you cannot forget at the call site. Skip this step and you get “Model not found” in Horizon while the HTTP request still returned 201.\u003C\u002Fp>\n\n\u003Ch2 id=\"real-world-example\">Real-World Example\u003C\u002Fh2>\n\u003Cp>Laravel API, Redis queue, checkout: create \u003Ccode>orders\u003C\u002Fcode>, decrement \u003Ccode>products.stock\u003C\u002Fcode>, dispatch \u003Ccode>ProcessOrder\u003C\u002Fcode>. Without a transaction, stock update hit a check constraint (stock would go negative) after the order \u003Ccode>INSERT\u003C\u002Fcode>. You had an unpaid order and full stock. Support thought payments were broken. They were not. The second write failed and the first stayed.\u003C\u002Fp>\n\u003Cp>Wrapping both writes fixed the orphan. Then Horizon blew up: the job ran, \u003Ccode>Order::findOrFail($id)\u003C\u002Fcode> 404d. The worker was faster than \u003Ccode>COMMIT\u003C\u002Fcode>. Cause: dispatch sat inside the closure. Fix: \u003Ccode>DB::afterCommit()\u003C\u002Fcode> around the dispatch (or \u003Ccode>$afterCommit\u003C\u002Fcode> on the job). Request still returns 201 only after both rows exist; the job only runs on a committed order.\u003C\u002Fp>\n\n\u003Ch2 id=\"pros-cons\">Pros &amp; Cons\u003C\u002Fh2>\n\u003Ch3>Advantages\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Two writes stay paired. The failure mode is an exception, not a silent half-row.\u003C\u002Fli>\n\u003Cli>Deadlock retries are one integer, not a custom loop around \u003Ccode>40001\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>You stay on the same mental model as SQL. Anyone who knows \u003Ccode>BEGIN\u003C\u002Fcode> can read the code.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Disadvantages\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Open transactions hold locks. A HTTP call or a huge report inside the closure stalls other checkouts. Keep the closure short.\u003C\u002Fli>\n\u003Cli>Nested calls are savepoints. An inner “commit” does not publish rows. If you thought it did, you will debug ghosts.\u003C\u002Fli>\n\u003Cli>No help on MyISAM, and no help for Redis \u002F files \u002F HTTP. Those need their own rollback story, or you do not call them yet.\u003C\u002Fli>\n\u003C\u002Ful>\n\n\u003Ch2 id=\"best-practices\">Best Practices\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Lock the rows you are about to change (\u003Ccode>lockForUpdate()\u003C\u002Fcode>) so two checkouts cannot overdraw the same stock.\u003C\u002Fli>\n\u003Cli>Throw to abort. Returning \u003Ccode>null\u003C\u002Fcode> or catching inside the closure and swallowing it commits the partial work.\u003C\u002Fli>\n\u003Cli>Keep HTTP, sleep, and mail out of the closure. Database work only; side effects in \u003Ccode>afterCommit\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>Set attempts on hot paths (checkout, wallets). One deadlock should retry, not page the user a 500.\u003C\u002Fli>\n\u003Cli>Use one connection. Switching connections mid-closure splits the transaction into two, which is the bug you were avoiding.\u003C\u002Fli>\n\u003C\u002Ful>\n\n\u003Ch2 id=\"common-mistakes\">Common Mistakes\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Cstrong>Catching the exception inside the closure\u003C\u002Fstrong> — Laravel sees a clean return and commits. \u003Cstrong>Fix:\u003C\u002Fstrong> rethrow, or do not catch there. Handle it in the controller after rollback.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Dispatching a job that reads the new row immediately\u003C\u002Fstrong> — worker wins the race against commit. \u003Cstrong>Fix:\u003C\u002Fstrong> \u003Ccode>DB::afterCommit()\u003C\u002Fcode> or \u003Ccode>public bool $afterCommit = true\u003C\u002Fcode> on the job.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Wrapping a single \u003Ccode>save()\u003C\u002Fcode>\u003C\u002Fstrong> — extra lock time, no extra safety. \u003Cstrong>Fix:\u003C\u002Fstrong> wrap only when two statements must succeed together.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Forgetting \u003Ccode>lockForUpdate()\u003C\u002Fcode> on balances\u002Fstock\u003C\u002Fstrong> — the transaction is atomic per request, not safe across two concurrent requests. \u003Cstrong>Fix:\u003C\u002Fstrong> lock, then read, then write.\u003C\u002Fli>\n\u003C\u002Ful>\n\n\u003Ch2 id=\"frequently-asked-questions\">Frequently Asked Questions\u003C\u002Fh2>\n\u003Ch3 id=\"faq-what-is-laravel-database-transactions\">What is DB::transaction() in Laravel?\u003C\u002Fh3>\n\u003Cp>It is a helper that starts a database transaction, runs your closure, commits on success, and rolls back if the closure throws. It maps to SQL BEGIN\u002FCOMMIT\u002FROLLBACK on InnoDB or Postgres. It does not roll back queues, mail, or HTTP calls unless you defer those with afterCommit.\u003C\u002Fp>\n\n\u003Ch3 id=\"faq-how-to\">How do I use DB::transaction() in Laravel?\u003C\u002Fh3>\n\u003Cp>Pass a closure with the writes, and optionally a retry count: \u003Ccode>DB::transaction(function () { \u002F* writes *\u002F }, 3);\u003C\u002Fcode>. Throw on business failure so the rollback happens. Put jobs and mail in \u003Ccode>DB::afterCommit()\u003C\u002Fcode>. Verify by throwing on purpose and checking that no rows changed.\u003C\u002Fp>\n\n\u003Ch3 id=\"faq-vs\">DB::transaction() vs beginTransaction() \u002F commit() \u002F rollBack()?\u003C\u002Fh3>\n\u003Cp>Use \u003Ccode>DB::transaction()\u003C\u002Fcode> for almost all app code — less chance you forget \u003Ccode>rollBack()\u003C\u002Fcode> on an exception. Use the manual trio when you must commit in stages across methods you do not control, or when a package already opened the transaction. Same SQL underneath; the closure is harder to get wrong.\u003C\u002Fp>\n\n\u003Ch3 id=\"faq-worth-it\">Is DB::transaction() worth it?\u003C\u002Fh3>\n\u003Cp>Yes, whenever one action writes two or more rows that must stay consistent. No, when you are reading, updating one row, or wrapping work that is not in the database. The cost is lock time, so keep the closure small and lock only the rows you need.\u003C\u002Fp>\n\n\u003Ch3 id=\"faq-nested\">Do nested DB::transaction() calls work?\u003C\u002Fh3>\n\u003Cp>They run as savepoints. The inner closure can roll back to the savepoint; the outer transaction still decides when data is visible. Do not assume an inner success is a real commit. Prefer one outer transaction in application code unless a library forced the inner call.\u003C\u002Fp>\n\n\u003Ch2 id=\"summary\">Summary\u003C\u002Fh2>\n\u003Cp>Use \u003Ccode>DB::transaction()\u003C\u002Fcode> when a single user action has to change more than one row and a partial write would be a data bug. Laravel will commit a clean closure and roll back a thrown exception. That is the whole contract.\u003C\u002Fp>\n\u003Cp>Today: pick one checkout or transfer in your app, wrap the writes, add \u003Ccode>lockForUpdate()\u003C\u002Fcode>, and move the job dispatch to \u003Ccode>afterCommit\u003C\u002Fcode>. Then force a throw once and confirm both tables stayed unchanged. If you want the request path around that controller, read the \u003Ca href=\"\u002Fblog\u002Flaravel-lifecycle\">Laravel request lifecycle\u003C\u002Fa> post next.\u003C\u002Fp>\n\n\u003Ch2 id=\"key-takeaways\">Key Takeaways\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Wrap multi-row writes in \u003Ccode>DB::transaction()\u003C\u002Fcode>; do not wrap a single \u003Ccode>save()\u003C\u002Fcode> or a read.\u003C\u002Fli>\n\u003Cli>Throw to roll back. A swallowed catch inside the closure commits the damage.\u003C\u002Fli>\n\u003Cli>Lock rows you will update (\u003Ccode>lockForUpdate()\u003C\u002Fcode>) or concurrent requests can still overdraw.\u003C\u002Fli>\n\u003Cli>Jobs, mail, and HTTP go in \u003Ccode>afterCommit\u003C\u002Fcode> — the database rollback cannot undo them.\u003C\u002Fli>\n\u003Cli>Deadlock retries are the second argument; nested calls are savepoints, not a second commit.\u003C\u002Fli>\n\u003C\u002Ful>","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1787114417893-hp3hmc.webp","Laravel DB::transaction() — When and Why to Use It","Wrap multi-table Laravel writes in DB::transaction() so failures roll back. Covers afterCommit, deadlock retries, savepoints, and when you can skip it.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fog\u002F1787116424325-o5kv11.webp",[19,20,21,22,23],"Laravel","Database","Eloquent","PHP","Transactions","published","2026-08-19T04:44:00.327+00:00",16,null,"","2026-08-19T04:43:11.515364+00:00","2026-08-19T05:14:18.190197+00:00",[32,47,63,79,93,107,119,131,144,156,167,169,181,194,208,219,230,239,250,264,276,285,296,309],{"id":33,"title":34,"slug":35,"excerpt":36,"cover_image":37,"tags":38,"published_at":44,"updated_at":45,"view_count":46},"1fac09f2-990e-4ebf-99b1-0cc532e7cb08","Soft Delete Inventory Bug — Phantom Serial Stock After Purchase Delete","soft-delete-inventory-bug-phantom-serial-stock-after-purchase-delete","Soft-deleting a purchase looked fine until serial-tracked products stayed sellable. The movement ran, quantity didn’t move, and serials were never detached.","https:\u002F\u002Fik.imagekit.io\u002F93se7t7h4e\u002Fportfolio\u002Fposts\u002Fblog\u002Fcovers\u002F1793165769172-Phantom-Inventory_-Deleted-Warehouse-Order_Z0BIZdhyJ.webp",[39,40,41,42,43,6],"laravel","inventory","soft-delete","serial-numbers","stock-movements","2026-10-28T05:36:31.148+00:00","2026-10-28T05:36:32.188948+00:00",21,{"id":48,"title":49,"slug":50,"excerpt":51,"cover_image":52,"tags":53,"published_at":61,"updated_at":62,"view_count":26},"b2a6b718-c6e5-42fa-9358-22e84035aaf2","Multi-Tenant Inventory Manager with Nuxt 3 and Supabase","multi-tenant-inventory-manager-nuxt-supabase","A shop-billing SaaS on Nuxt 3 and Supabase: stock, invoices, UPI links, AI bill scan, and per-shop storefronts — with RLS so shop_id is never trusted from the client.","https:\u002F\u002Fik.imagekit.io\u002F93se7t7h4e\u002Fportfolio\u002Fposts\u002Flibrary\u002F1792583563566-Modern-Retail-POS-Dashboard-Network_-BFGj_TT0.webp?updatedAt=1792583565092",[54,55,56,40,6,57,58,59,60],"nuxt","supabase","multi-tenancy","vue","pinia","vuetify","ai","2026-10-21T12:07:58.857+00:00","2026-10-21T12:07:59.070373+00:00",{"id":64,"title":65,"slug":66,"excerpt":67,"cover_image":68,"tags":69,"published_at":76,"updated_at":77,"view_count":78},"58f0adc6-f4e9-4501-bc0e-ab83cc2cc073","Laravel Sanctum 419 Fix — Why XSRF-TOKEN Must Stay Encrypted","laravel-sanctum-419-xsrf-token-encryption","Sanctum SPA login kept returning 419 CSRF token mismatch. The bug wasn’t domains or cookies “not sticking” — it was excluding XSRF-TOKEN from EncryptCookies while Laravel decrypts the X-XSRF-TOKEN header.","https:\u002F\u002Fik.imagekit.io\u002F93se7t7h4e\u002Fportfolio\u002Fposts\u002Fblog\u002Fcovers\u002F1792229994752-From-CSRF-Error-to-Secure-Fix_FIVIW5po2.webp",[19,70,71,72,73,74,75],"Sanctum","CSRF","419","SPA","Nuxt","API Authentication","2026-10-17T09:40:04.212+00:00","2026-10-17T09:40:06.051151+00:00",17,{"id":80,"title":81,"slug":82,"excerpt":83,"cover_image":84,"tags":85,"published_at":90,"updated_at":91,"view_count":92},"7b4bee90-b35b-4ced-ae8c-0a71e7d968fb","ImageKit Nuxt Upload — Keep Private Keys Off the Client","imagekit-nuxt-upload-secure","ImageKit Nuxt upload means the browser never sees your private key. Sign or upload on the server, return a CDN URL, and store that URL in your CMS or database.","https:\u002F\u002Fik.imagekit.io\u002F93se7t7h4e\u002Fportfolio\u002Fposts\u002Fblog\u002Fcovers\u002F1792216420019-Secure-Upload-Architecture-Flow_MGyvtL5tR.webp",[74,86,87,88,89],"ImageKit","Vue","TypeScript","SEO","2026-10-17T05:55:24.556+00:00","2026-10-17T05:55:24.735773+00:00",23,{"id":94,"title":95,"slug":96,"excerpt":97,"cover_image":98,"tags":99,"published_at":105,"updated_at":106,"view_count":26},"bd55b3c6-8bd3-447d-99ad-d46a97490d7b","Apache 2 Installation on Ubuntu: Step-by-Step","apache-2-installation-ubuntu","Install Apache 2 on Ubuntu with apt, start the service, open the firewall, and verify the default page. Part 2 of the Apache 2 series — clean setup before virtual hosts.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1788925690969-7zm2c2.webp",[100,101,102,103,104],"Apache","Ubuntu","Installation","Linux","Web Server","2026-09-09T03:49:25.809+00:00","2026-09-09T03:49:26.679843+00:00",{"id":108,"title":109,"slug":110,"excerpt":111,"cover_image":112,"tags":113,"published_at":116,"updated_at":117,"view_count":118},"8c75a723-b1a7-4fab-9bb9-71a111c9d4f8","Apache vs Nginx: What They Are and When to Use Each","apache-vs-nginx","Apache and Nginx are web servers. They take HTTP requests and return files or pass work to PHP, Node, or another app. Apache fits shared hosting and .htaccess; Nginx is the usual reverse proxy on an Ubuntu VPS.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1788524039845-wrez6s.webp",[100,114,101,104,103,115],"Nginx","DevOps","2026-09-04T12:14:08.218+00:00","2026-09-04T12:14:08.430018+00:00",9,{"id":120,"title":121,"slug":122,"excerpt":123,"cover_image":124,"tags":125,"published_at":128,"updated_at":129,"view_count":130},"40dd3304-99d2-4948-b8c1-44625f1f4306","What Is a Virtual Host? Host Multiple Sites on One Ubuntu VPS","virtual-host-linux-multiple-websites","A virtual host maps each domain to its own folder on one server. Developers use this on Ubuntu VPSes so portfolio, API, and staging share one bill. Same idea on any Linux — Ubuntu is just what most tutorials and clouds default to.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1788523755345-javhet.webp",[126,101,114,103,127,115],"Virtual Host","VPS","2026-09-04T12:09:22.623+00:00","2026-09-04T12:09:22.931401+00:00",12,{"id":132,"title":133,"slug":134,"excerpt":135,"cover_image":136,"tags":137,"published_at":141,"updated_at":142,"view_count":143},"6e45f39b-1ade-47f0-a0b0-b4cd386a10dc","Laravel Queues & Jobs: How Background Processing Works","laravel-queues-and-jobs","Laravel queues move slow work off the HTTP request. You push a Job onto a queue, a worker runs it later, and the user gets a fast response. Use them for mail, webhooks, image work, and anything that can fail and retry.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1787286979145-0i7ewp.webp",[19,138,139,22,140],"Queues","Jobs","backend","2026-08-21T04:36:56.222+00:00","2026-08-21T04:36:56.606735+00:00",20,{"id":145,"title":146,"slug":147,"excerpt":148,"cover_image":149,"tags":150,"published_at":153,"updated_at":154,"view_count":155},"938c7bd9-2cf3-4a81-8dae-cf88c09e64ca","Laravel N+1 Query Problem: How to Detect and Fix It","laravel-n-plus-1-query-problem","The Laravel N+1 query problem is when one listing query is followed by one extra query per row. You spot it in Telescope or the query log, then fix it with with(), withCount(), and nested eager loads.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1787199419649-niq9k8.webp",[19,21,151,152,22],"N+1","performance","2026-08-20T04:17:43.609+00:00","2026-08-20T05:50:24.297698+00:00",14,{"id":157,"title":158,"slug":159,"excerpt":160,"cover_image":161,"tags":162,"published_at":164,"updated_at":165,"view_count":166},"76717847-4080-4ae6-a2d8-b35badc46be3","Laravel Eloquent Relationships","laravel-eloquent-relationships","Laravel Eloquent relationships map how models connect — hasMany, belongsTo, belongsToMany, and more. Define them once, then load related rows with with() instead of stuffing joins into every query.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1787122982331-16979e.webp",[19,21,22,163,140],"ORM","2026-08-19T07:03:17.721+00:00","2026-08-20T04:19:08.829027+00:00",18,{"id":9,"title":10,"slug":11,"excerpt":12,"cover_image":14,"tags":168,"published_at":25,"updated_at":30,"view_count":26},[19,20,21,22,23],{"id":170,"title":171,"slug":172,"excerpt":173,"cover_image":174,"tags":175,"published_at":179,"updated_at":180,"view_count":155},"d1020b7b-b410-414f-9ceb-eb0501bc905e","Laravel Auditing Package — Track Model Changes the Right Way","laravel-auditing-package","The Laravel auditing package records old and new model values, the user who changed them, and when it happened—without you inventing a second history table for every feature.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1786778101029-mwb9sf.webp",[19,176,22,177,178],"Auditing","Security","Activity Log","2026-08-15T21:24:32.135+00:00","2026-08-15T21:24:32.194447+00:00",{"id":182,"title":183,"slug":184,"excerpt":185,"cover_image":186,"tags":187,"published_at":191,"updated_at":192,"view_count":193},"3d5eb867-6288-48c4-af04-8b7ece8b874e","Laravel Lifecycle — How a Request Becomes a Response","laravel-lifecycle","The Laravel lifecycle is the path from HTTP request to response: bootstrap, service providers, middleware, routing, then the controller. Know that path and most “random” bugs stop being random.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1786777544862-khxf92.webp",[19,22,188,189,190],"Request Lifecycle","Middleware","Backend","2026-08-15T07:15:13.877+00:00","2026-08-15T07:15:13.978037+00:00",11,{"id":195,"title":196,"slug":197,"excerpt":198,"cover_image":199,"tags":200,"published_at":206,"updated_at":207,"view_count":155},"2ab5e08a-7117-43c5-87eb-0789a2fd3af4","Claude Code Best Practices for Large Codebases — Scope Before You Ship","claude-code-best-practices-large-codebases","On a big repo, Claude Code only helps if you lock rules in CLAUDE.md, scope every ticket, plan multi-file edits, and review the diff like a PR.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1786178453897-dulbmv.webp",[201,202,203,204,205],"claude-code","ai-coding","large-codebases","monorepo","developer-tools","2026-08-08T08:41:03.571+00:00","2026-08-08T08:41:03.839922+00:00",{"id":209,"title":210,"slug":211,"excerpt":212,"cover_image":213,"tags":214,"published_at":217,"updated_at":218,"view_count":166},"ddd55ce1-48fd-40b4-ae91-48a6bec20a2a","Nuxt Middleware Explained — Auth, Redirects & Route Guards Deep Dive","nuxt-middleware-explained","Nuxt middleware runs before a page loads so you can check auth, redirect users, or block a route — on the server for the first hit and in the browser on later navigations.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1785902953511-osy6pt.webp",[74,189,215,216,87],"SSR","Auth","2026-08-05T04:09:38.347+00:00","2026-08-05T04:09:38.496803+00:00",{"id":220,"title":221,"slug":222,"excerpt":223,"cover_image":224,"tags":225,"published_at":228,"updated_at":229,"view_count":130},"e0d9941b-467d-45cc-bf12-45390cf9aeaa","Nuxt Lifecycle Explained — Server, Client & Hooks Made Simple","nuxt-lifecycle-explained","Nuxt lifecycle is the order your app boots, fetches data, renders HTML on the server, hydrates in the browser, then runs page navigation — so you know where to put code safely.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1785901639981-9tgcl5.webp",[74,87,215,226,227],"Lifecycle","JavaScript","2026-08-05T03:54:08.301+00:00","2026-08-05T03:54:08.919676+00:00",{"id":231,"title":232,"slug":233,"excerpt":234,"cover_image":235,"tags":236,"published_at":237,"updated_at":238,"view_count":92},"23c9cf92-232b-460f-9825-a9c53e350600","How to Use Laravel Sanctum for API Authentication — SPA Cookies & Tokens","laravel-api-authentication","Laravel Sanctum authenticates first-party SPAs with secure cookies and issues API tokens for mobile or third-party clients—without the complexity of full OAuth.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1785833713437-wcqb6c.webp",[19,70,75,22,73,177],"2026-08-04T08:56:17.304+00:00","2026-08-06T04:07:09.059636+00:00",{"id":240,"title":241,"slug":242,"excerpt":243,"cover_image":244,"tags":245,"published_at":248,"updated_at":249,"view_count":166},"f50b774a-c745-41aa-a3b0-72ac1f5b7117","Laravel Sanctum vs Passport — Which API Auth Should You Use?","laravel-sanctum-vs-passport","Laravel Sanctum is the lighter choice for SPAs and simple API tokens; Passport is full OAuth2 for third-party apps. Pick Sanctum for most apps, Passport when you need real OAuth2.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1785817155174-054d6s.webp",[19,70,246,75,22,247,73],"Passport","OAuth2","2026-08-04T04:19:37.286+00:00","2026-08-04T04:49:08.25034+00:00",{"id":251,"title":252,"slug":253,"excerpt":254,"cover_image":255,"tags":256,"published_at":261,"updated_at":262,"view_count":263},"ef36ca16-73ab-4f9a-9584-ff70a60da5f5","Laravel vs NestJS in 2026: Which Backend Should US Startups Choose?","laravel-vs-nestjs-2026-us-startups","Laravel vs NestJS for US startups in 2026: compare speed, TypeScript, hiring, SaaS MVPs, and real-time apps — and pick the backend that matches your team.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1785609396341-ungcby.jpg",[19,257,190,258,259,22,88,260],"NestJS","SaaS","Startups","Web Development","2026-08-01T18:40:05.071+00:00","2026-08-01T18:40:05.261242+00:00",38,{"id":265,"title":266,"slug":267,"excerpt":268,"cover_image":269,"tags":270,"published_at":274,"updated_at":275,"view_count":130},"c4e41758-834c-476e-8830-f776c963a784","What Is TypeScript? A Beginner’s Guide to Safer JavaScript","what-is-typescript","TypeScript is JavaScript with types. Learn what it is, how it works, and how to write your first typed script with clear examples and FAQs.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1785574204088-8bc8es.jpg",[88,227,260,271,272,273],"Programming","Beginners","Frontend","2026-08-01T08:50:45.861+00:00","2026-08-01T08:50:45.958378+00:00",{"id":277,"title":278,"slug":279,"excerpt":280,"cover_image":281,"tags":282,"published_at":283,"updated_at":284,"view_count":155},"37ee32f1-7b8d-4c4d-92b4-37bb37ff64c5","What Is JavaScript? A Beginner’s Guide to Modern Web Development","what-is-javascript","JavaScript is the programming language that makes websites interactive. Learn what it is, how it works, and how to write your first script with clear examples and FAQs.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1785561346515-utrr91.jpg",[227,260,271,272,273],"2026-08-01T05:16:12.728+00:00","2026-08-01T08:50:11.164531+00:00",{"id":286,"title":287,"slug":288,"excerpt":289,"cover_image":290,"tags":291,"published_at":294,"updated_at":295,"view_count":166},"f238da13-8416-41e6-8281-a6185efd4bd4","Laravel Sanctum Explained: Simple API Authentication for Modern Apps","laravel-sanctum-api-authentication","Laravel Sanctum makes API authentication simple — whether you need token-based APIs for mobile apps or cookie-based auth for SPAs. Here’s how it works, without the jargon.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1785470074981-vejfi4.jpg",[19,70,292,293,73],"API","Authentication","2026-08-01T04:13:15.178+00:00","2026-08-01T08:50:11.393519+00:00",{"id":297,"title":298,"slug":299,"excerpt":300,"cover_image":301,"tags":302,"published_at":306,"updated_at":307,"view_count":308},"d8c77913-46f4-4012-ade6-bd5a81676001","Laravel Module Structure Explained: Keep Large Apps Clean","laravel-module-structure-explained","A practical guide to Laravel module architecture — folder layout, providers, routes, and boundaries that keep features independent as your app grows.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1785385385865-8oyk12.png",[19,22,303,304,190,305],"Modules","Architecture","Clean Code","2026-07-30T04:54:17.431+00:00","2026-08-01T08:50:11.599795+00:00",6,{"id":310,"title":311,"slug":312,"excerpt":313,"cover_image":314,"tags":315,"published_at":322,"updated_at":323,"view_count":143},"26ccd19c-a8bb-419d-be11-efd1d221b415","Cursor vs Claude vs ChatGPT: Which AI Actually Helps with Laravel & Nuxt?","cursor-ai-vs-claude-code-vs-chatgpt-for-laravel-nuxt-development-2026","Tired of constantly copying and pasting code between your Vue frontend and PHP backend? I tested Cursor, Claude Code, and ChatGPT to see which one actually speeds up a real-world Laravel and Nuxt workflow. Here is my breakdown.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1785300697566-pn766r.png",[19,316,317,318,319,320,321],"Nuxt 3","AI for Developers","Cursor","Claude Code","ChatGPT","Full Stack","2026-07-29T04:46:50.88+00:00","2026-08-01T08:50:11.809909+00:00",{"variant":325,"profile":330,"heroStats":343,"aboutParagraphs":347,"aboutPillars":354,"aboutFacts":367,"skillCategories":380,"experiences":419,"education":446,"projects":465,"languages":535,"interests":538},{"id":326,"slug":327,"label":328,"is_active":329,"sort_order":4},"481b2725-e0f6-43df-beea-937ec806a438","full-stack-developer","Full Stack Developer",true,{"name":331,"title":332,"tagline":332,"photo_url":333,"summary":334,"email":335,"phone":28,"location":336,"linkedin":337,"github":338,"instagram":339,"hero_headline":340,"hero_headline_accent":341,"hero_subheadline":342},"Mohd Anish","Full Stack Developer ","\u002Fprofile.png","Full Stack Developer with 3.5+ years of experience specializing in Laravel, Vue.js, Nuxt.js, MySQL, and modern web technologies. Experienced in designing, developing, and maintaining scalable web applications with a strong focus on performance, security, and code quality.","anhali736@gmail.com","Rajasthan, India","linkedin.com\u002Fin\u002Fmohd-anish-23096635a","https:\u002F\u002Fgithub.com\u002Fmrmolani76","https:\u002F\u002Fwww.instagram.com\u002Fmohdanish.me\u002F","Building Scalable Web Apps","using Modern Technologies","Building secure, scalable, and high-performance web applications using Laravel, Vue.js, Nuxt.js, and MySQL.",[344],{"value":345,"label":346},"3.5+","Yrs Development",[348,350,352],{"html":349},"I'm a \u003Cspan class=\"text-gold font-medium\">Full Stack Developer\u003C\u002Fspan> passionate about building secure, scalable, and high-performance web applications. I enjoy solving complex problems and creating modern digital experiences with clean, maintainable code.",{"html":351},"I specialize in \u003Cspan class=\"text-gold font-medium\">Laravel\u003C\u002Fspan>, \u003Cspan class=\"text-foreground\">Vue.js\u003C\u002Fspan>, \u003Cspan class=\"text-foreground\">Nuxt.js\u003C\u002Fspan>, \u003Cspan class=\"text-foreground\">MySQL\u003C\u002Fspan>, and \u003Cspan class=\"text-foreground\">REST APIs\u003C\u002Fspan>, building responsive and scalable applications with a strong focus on performance, security, and code quality.",{"html":353},"With \u003Cspan class=\"text-foreground\">3.5+ years of experience\u003C\u002Fspan>, I've contributed to enterprise-grade applications, including compliance-critical modules for the \u003Cspan class=\"text-foreground\">Complere eQMS\u003C\u002Fspan> platform. I'm committed to continuous learning and building software that is reliable, maintainable, and ready for real-world use.",[355,359,363],{"icon":356,"label":357,"description":358},"lucide:code-2","Build","Scalable, clean web apps",{"icon":360,"label":361,"description":362},"lucide:trending-up","Grow","Marketing-driven results",{"icon":364,"label":365,"description":366},"lucide:shield-check","Ship","Reliable, compliant systems",[368,372,376],{"icon":369,"label":370,"value":371},"lucide:settings","Core Stack","Laravel · Nuxt · Vue · MySQL",{"icon":373,"label":374,"value":375},"lucide:building-2","Currently","Complibued — eQMS Platform",{"icon":377,"label":378,"value":379},"lucide:map-pin","Availability","Open to opportunities",[381,394,403,414],{"title":382,"icon":383,"color":384,"show_on_home":329,"show_on_resume":329,"skills":385},"Backend Development","lucide:database","from-gold-soft to-gold-deep",[19,22,386,387,388,389,390,391,392,393],"Supabase (BaaS)","MySQL","REST APIs","Git","Docker","Redis","GitHub Actions","Cloudflare",{"title":395,"icon":396,"color":384,"show_on_home":329,"show_on_resume":397,"skills":398},"Frontend Development","lucide:code",false,[399,400,401,88,402,227],"Nuxt.js","Vue.js","React","Tailwind CSS",{"title":404,"icon":405,"color":384,"show_on_home":329,"show_on_resume":397,"skills":406},"AI & Automation","lucide:zap",[407,408,409,410,411,412,413],"Prompt Engineering","ChatGPT & Claude","Google Gemini","AI Grok","GitHub Copilot","AI Content Strategy","Workflow Automation",{"title":415,"icon":416,"color":384,"show_on_home":329,"show_on_resume":329,"skills":417},"Development","lucide:wrench",[19,22,400,399,227,88,402,388,387,418],"Git & GitHub",[420],{"role":328,"company":421,"note":422,"period":423,"description":424,"stack":425,"color":384,"icon":426,"points":427},"Complibued","Complere eQMS — Pharmaceutical SaaS","2023 – Present","Building Complere eQMS, a cloud-based Quality Management System for regulated life sciences using Laravel and Nuxt.js. Developed compliance-critical modules — Document Control, LMS, Events, CAPA, Change Control, Audit, and Risk Assessment.","Laravel · Vue\u002FNuxt · MySQL · Tailwind CSS","lucide:folder-git-2",[428,431,433,435,437,440,442,444],{"text":429,"surface":430},"Developing and maintaining a pharma-focused eQMS platform using Laravel and Nuxt.js.","resume",{"text":432,"surface":430},"Built compliance-critical modules: Document Control, Training (LMS), Event Handling, CAPA, Change Control (CR), Audit, and Risk Assessment (RA).",{"text":434,"surface":430},"Implemented approval workflows, version control, and immutable audit trails aligned to 21 CFR Part 11.",{"text":436,"surface":430},"Collaborated with QA teams to meet pharmaceutical compliance standards.",{"text":438,"surface":439},"Built Document Control & LMS (training) modules","home",{"text":441,"surface":439},"Implemented CAPA and Event management workflows",{"text":443,"surface":439},"Developed Change Control (CR) with impact-assessed approvals",{"text":445,"surface":439},"Delivered Audit & Risk Assessment (RA) modules with audit trails",[447,452,456,461],{"degree":448,"school":449,"period":450,"score":451},"M.Sc. (Computer Science)","MDS University, Ajmer","2023 – 2025","73%",{"degree":453,"school":449,"period":454,"score":455},"BCA","2020 – 2023","71%",{"degree":457,"school":458,"period":459,"score":460},"Senior Secondary (12th)","RBSE, Ajmer","2018 – 2019","68.80%",{"degree":462,"school":458,"period":463,"score":464},"Secondary (10th)","2016 – 2017","48.75%",[466,483,500],{"title":467,"slug":468,"description":469,"why":470,"category":471,"image":472,"emoji":473,"link":474,"is_active":329,"stack":475,"features":477,"metrics":482},"Inventory Manager","inventory-manager","Professional inventory management system for tracking stock, orders, and enterprise operations. Powered by Supabase auth and a relational MySQL backend.","Stock and order tracking needed a reliable source of truth for enterprise operations. This system was built so teams can monitor inventory, manage orders, and report status from one authenticated app.","Enterprise","bg-gradient-to-br from-gold-soft\u002F15 via-gold\u002F5 to-transparent","📦","https:\u002F\u002Fruby-enterprise.vercel.app\u002F",[400,476,387,402,88],"Supabase",[478,479,480,481],"Stock Tracking","Order Management","User Authentication","Reporting & Analytics",[],{"title":484,"slug":485,"description":486,"why":487,"category":488,"image":489,"emoji":490,"link":491,"is_active":329,"stack":492,"features":494,"metrics":499},"Random Video Chat","random-video-chat","Omegle-style platform for spontaneous 1-on-1 video conversations with strangers. Uses WebRTC for peer-to-peer video and Supabase Realtime for matchmaking and signaling.","I wanted to explore real-time peer connections without a heavy media server. The app was built to practice WebRTC + realtime matchmaking and deliver instant 1-on-1 video chat with no account friction.","Real-time","bg-gradient-to-br from-gold\u002F15 via-gold\u002F5 to-transparent","🎥","https:\u002F\u002Fomegle-seven-xi.vercel.app\u002F",[400,493,476,402,88],"WebRTC",[495,496,497,498],"Peer-to-Peer Video","Random Matchmaking","Realtime Signaling","No Sign-up Required",[],{"title":501,"slug":502,"description":503,"why":504,"category":505,"image":489,"emoji":506,"link":507,"is_active":329,"stack":508,"features":516,"metrics":525},"Nexro","nexro","Multi-tenant retail web app for GST billing and inventory — products, purchases, sales, POS, quotations, supplier ledgers, and reports. Landing page: nexro.me.","Retail shops were juggling billing, stock, purchases, and supplier dues across sheets and separate tools. Nexro was built as a multi-tenant SaaS so each shop gets its own data on a shared Laravel + Nuxt stack, with GST invoices, live stock, and day-to-day ops from one login.","Web App \u002F SaaS","🏪","https:\u002F\u002Fnexro.me",[509,510,511,512,402,88,387,513,514,515,390],"Laravel 12","Nuxt 4","Vue 3","Vuetify 3","stancl\u002Ftenancy","Laravel Sanctum","Spatie Permission",[517,518,519,520,521,522,523,524],"Multi-tenant shop isolation","GST billing & POS","Inventory with SKU \u002F barcode \u002F serial","Purchases & supplier ledger","Quotations → invoice","Sales, stock & dues reports","Thermal & A4 print","Region-aware landing (nexro.me)",[526,529,532],{"value":527,"label":528},"1","Product platform",{"value":530,"label":531},"7+","Core modules",{"value":533,"label":534},"MT","Multi-tenant",[536,537],"Hindi","English",[260,539,540],"Video Content","New Tools & Tech",[]]