[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"site-settings":3,"blog-post:laravel-sanctum-419-xsrf-token-encryption":8,"blog-comments:58f0adc6-f4e9-4501-bc0e-ab83cc2cc073":32,"blog-posts-latest:24":33,"site-content":324},{"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":26,"published_at":27,"view_count":28,"deleted_at":29,"deleted_reason":30,"created_at":31,"updated_at":31},"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.","\u003Ch2 id=\"quick-answer\">Quick Answer\u003C\u002Fh2>\n\u003Cp>A Laravel Sanctum 419 on SPA cookie auth often means the CSRF token never matched — not that your password is wrong. If you excluded \u003Ccode>XSRF-TOKEN\u003C\u002Fcode> from cookie encryption so the frontend could “read it,” Laravel 11\u002F12 still \u003Cstrong>decrypts\u003C\u002Fstrong> the \u003Ccode>X-XSRF-TOKEN\u003C\u002Fcode> header. Decrypt fails, the token becomes empty, and every stateful POST dies with CSRF token mismatch.\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 Sanctum 419 \u002F XSRF-TOKEN encryption\u003C\u002Ftd>\u003C\u002Ftr>\n\u003Ctr>\u003Ctd>Category\u003C\u002Ftd>\u003Ctd>Laravel \u002F Sanctum \u002F SPA Auth\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-sanctum-419\">What Is a Laravel Sanctum 419?\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-sanctum-419\">What Is a Laravel Sanctum 419?\u003C\u002Fh2>\n\u003Cp>It’s not “Sanctum is broken.” HTTP 419 here means Laravel’s CSRF middleware rejected the request before your login controller ran. For first-party SPAs, Sanctum uses session cookies: you hit \u003Ccode>\u002Fsanctum\u002Fcsrf-cookie\u003C\u002Fcode>, then send mutating requests with the session cookie plus an \u003Ccode>X-XSRF-TOKEN\u003C\u002Fcode> header copied from the \u003Ccode>XSRF-TOKEN\u003C\u002Fcode> cookie.\u003C\u002Fp>\n\u003Cp>If that header doesn’t match the session’s \u003Ccode>_token\u003C\u002Fcode>, you get \u003Ccode>{\"message\":\"CSRF token mismatch.\"}\u003C\u002Fcode>. Bad credentials would be 401 from the controller. 419 means you never got that far.\u003C\u002Fp>\n\n\u003Ch2 id=\"why-it-matters\">Why It Matters\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Cstrong>Total write outage\u003C\u002Fstrong> — login, logout, and every cookie-session POST can fail at once.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Misleading debugging\u003C\u002Fstrong> — teams chase CORS, Redis, Cloudflare, and “cookie not set” for hours.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>False “fixes”\u003C\u002Fstrong> — excluding \u003Ccode>XSRF-TOKEN\u003C\u002Fcode> from encryption looks clever and breaks Laravel’s own CSRF path.\u003C\u002Fli>\n\u003C\u002Ful>\n\n\u003Ch2 id=\"how-it-works\">How It Works\u003C\u002Fh2>\n\u003Cp>Three pieces have to agree on one token value.\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cstrong>Session\u003C\u002Fstrong> — Laravel stores \u003Ccode>_token\u003C\u002Fcode> in the session (often Redis).\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Cookie\u003C\u002Fstrong> — \u003Ccode>XSRF-TOKEN\u003C\u002Fcode> is set for the SPA to echo. With normal \u003Ccode>EncryptCookies\u003C\u002Fcode>, that cookie is encrypted on the way out.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Header\u003C\u002Fstrong> — the SPA sends \u003Ccode>X-XSRF-TOKEN\u003C\u002Fcode> (usually URL-decoded cookie value). \u003Ccode>VerifyCsrfToken::getTokenFromRequest()\u003C\u002Fcode> \u003Cstrong>decrypts\u003C\u002Fstrong> that header, then compares it to the session token.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>If the cookie was left plaintext because you called something like \u003Ccode>encryptCookies(['XSRF-TOKEN'])\u003C\u002Fcode> as an exclusion, \u003Ccode>decrypt()\u003C\u002Fcode> throws, Laravel sets the token to \u003Ccode>''\u003C\u002Fcode>, and \u003Ccode>tokensMatch()\u003C\u002Fcode> fails → 419 every time.\u003C\u002Fp>\n\u003Cp>The SPA does not need to understand the cookie bytes. It only needs to copy them back. Encryption on the wire is fine.\u003C\u002Fp>\n\n\u003Ch2 id=\"step-by-step-guide\">Step-by-Step Guide\u003C\u002Fh2>\n\n\u003Ch3 id=\"step-1\">Step 1: Prove it’s CSRF, not credentials\u003C\u002Fh3>\n\u003Cp>With a fresh cookie jar:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>GET \u002Fsanctum\u002Fcsrf-cookie\nPOST \u002Fapi\u002Flogin   (or your SaaS login) with session cookie + X-XSRF-TOKEN\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Done check: if you see \u003Ccode>419 CSRF token mismatch\u003C\u002Fcode>, CSRF failed. If you see \u003Ccode>401\u003C\u002Fcode> with a credentials message, CSRF passed and the controller ran. That’s the split you want when testing a fix.\u003C\u002Fp>\n\n\u003Ch3 id=\"step-2\">Step 2: Inspect the XSRF-TOKEN cookie shape\u003C\u002Fh3>\n\u003Cp>After \u003Ccode>\u002Fsanctum\u002Fcsrf-cookie\u003C\u002Fcode>, look at \u003Ccode>XSRF-TOKEN\u003C\u002Fcode>:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Short plaintext-looking value (e.g. ~40 hex chars) while you \u003Cem>excluded\u003C\u002Fem> it from encryption → suspicious.\u003C\u002Fli>\n\u003Cli>Long encrypted payload (hundreds of chars) → normal Laravel encrypted cookie.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Also confirm Redis\u002Fsession \u003Ccode>_token\u003C\u002Fcode> exists and is stable across the GET and POST. If session and cookie generation look fine but POSTs still 419, focus on decrypt of the header.\u003C\u002Fp>\n\n\u003Ch3 id=\"step-3\">Step 3: Remove the EncryptCookies exclusion\u003C\u002Fh3>\n\u003Cp>In Laravel 11\u002F12 bootstrap middleware setup, delete any exclusion that keeps \u003Ccode>XSRF-TOKEN\u003C\u002Fcode> plaintext “so the SPA can read it.” Let \u003Ccode>EncryptCookies\u003C\u002Fcode> encrypt it like other cookies.\u003C\u002Fp>\n\u003Cp>On the SPA: after csrf-cookie, read \u003Ccode>document.cookie\u003C\u002Fcode> (or your cookie helper), \u003Ccode>decodeURIComponent\u003C\u002Fcode> the value, send it as \u003Ccode>X-XSRF-TOKEN\u003C\u002Fcode>. Don’t keep a stale Nuxt \u003Ccode>useCookie\u003C\u002Fcode> copy from an earlier page load.\u003C\u002Fp>\n\u003Cp>Done check: same bad-password login now returns \u003Cstrong>401\u003C\u002Fstrong>, not 419. Good password returns 200. Cookie length jumps to the encrypted form.\u003C\u002Fp>\n\n\u003Ch2 id=\"real-world-example\">Real-World Example\u003C\u002Fh2>\n\u003Cp>Stack: Laravel 12 API + Nuxt SaaS SPA, Sanctum cookie sessions, Redis session driver, Cloudflare in front. Symptom: every stateful write on the SaaS panel and tenant apps returned 419 — including login.\u003C\u002Fp>\n\u003Cp>We ruled out the usual suspects first. Session id stuck. Redis \u003Ccode>_token\u003C\u002Fcode> matched what we thought the cookie was. Encoding tricks (\u003Ccode>%3D\u003C\u002Fcode> vs \u003Ccode>=\u003C\u002Fcode>) weren’t the root cause.\u003C\u002Fp>\n\u003Cp>The smoking gun was in \u003Ccode>VerifyCsrfToken\u003C\u002Fcode>: the header path decrypts. We had excluded \u003Ccode>XSRF-TOKEN\u003C\u002Fcode> from encryption with a comment that the SPA needed plaintext. That assumption was wrong. Removing the exclusion fixed production: encrypted cookie out, decrypt in, CSRF passes, controller finally answers 401\u002F200.\u003C\u002Fp>\n\u003Cp>Related trap on the same project: the SPA once rewrote only the hostname on a baked \u003Ccode>http:\u002F\u002Flocal:8080\u003C\u002Fcode> API URL and produced \u003Ccode>http:\u002F\u002Fsaas…:8080\u003C\u002Fcode> on HTTPS. That’s a separate origin bug. Fix CSRF encryption first; then make sure the browser calls the real same-origin \u003Ccode>https\u003C\u002Fcode> API.\u003C\u002Fp>\n\n\u003Ch2 id=\"pros-cons\">Pros &amp; Cons\u003C\u002Fh2>\n\u003Ch3>Advantages\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Keeping XSRF encrypted matches what Laravel’s CSRF middleware expects.\u003C\u002Fli>\n\u003Cli>One server change restores login and all cookie-session writes.\u003C\u002Fli>\n\u003Cli>Easy regression signal: bad login must be 401, never 419.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Disadvantages\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Cookie value is opaque — fine for echo-only clients; bad if you wrote custom JS that assumed a raw session token string.\u003C\u002Fli>\n\u003Cli>You still must decodeURIComponent the cookie before putting it in the header.\u003C\u002Fli>\n\u003Cli>Wrong API origin \u002F mixed content will still break CSRF even after this fix.\u003C\u002Fli>\n\u003C\u002Ful>\n\n\u003Ch2 id=\"best-practices\">Best Practices\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Treat 419 vs 401 as different bugs: CSRF vs credentials.\u003C\u002Fli>\n\u003Cli>Never exclude \u003Ccode>XSRF-TOKEN\u003C\u002Fcode> from \u003Ccode>EncryptCookies\u003C\u002Fcode> on modern Laravel.\u003C\u002Fli>\n\u003Cli>Re-read the cookie after \u003Ccode>\u002Fsanctum\u002Fcsrf-cookie\u003C\u002Fcode>; don’t trust a cached client token.\u003C\u002Fli>\n\u003Cli>Send credentials\u002Fcookies on CSRF + API calls; match \u003Ccode>SANCTUM_STATEFUL_DOMAINS\u003C\u002Fcode> to the real SPA host.\u003C\u002Fli>\n\u003Cli>Add a smoke test: stateful POST with echoed XSRF must not 419.\u003C\u002Fli>\n\u003C\u002Ful>\n\n\u003Ch2 id=\"common-mistakes\">Common Mistakes\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Cstrong>Plaintext XSRF “for the SPA”\u003C\u002Fstrong> — why: old blog advice \u002F wrong mental model. Fix: encrypt; SPA only echoes.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Forgetting decodeURIComponent\u003C\u002Fstrong> — why: cookie has \u003Ccode>%3D\u003C\u002Fcode>. Fix: decode before \u003Ccode>X-XSRF-TOKEN\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Blaming Sanctum when Origin is wrong\u003C\u002Fstrong> — why: baked \u003Ccode>http:\u002F\u002Fhost:8080\u003C\u002Fcode> on HTTPS. Fix: use page origin \u002F correct public API URL.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Testing without the session cookie\u003C\u002Fstrong> — why: request isn’t stateful, CSRF never runs, you see 401 and think CSRF is “fine” while the browser path still 419s.\u003C\u002Fli>\n\u003C\u002Ful>\n\n\u003Ch2 id=\"frequently-asked-questions\">Frequently Asked Questions\u003C\u002Fh2>\n\u003Ch3>What causes Laravel Sanctum 419 CSRF token mismatch?\u003C\u002Fh3>\n\u003Cp>The CSRF token from the header\u002Fsession didn’t match. Common SPA causes: wrong\u002Fmissing \u003Ccode>X-XSRF-TOKEN\u003C\u002Fcode>, stale cookie, domain\u002Fstateful config mistakes, or decrypt failure when \u003Ccode>XSRF-TOKEN\u003C\u002Fcode> was left unencrypted.\u003C\u002Fp>\n\u003Ch3>How do I fix Sanctum 419 on SPA login?\u003C\u002Fh3>\n\u003Cp>Call \u003Ccode>\u002Fsanctum\u002Fcsrf-cookie\u003C\u002Fcode>, echo the (decoded) \u003Ccode>XSRF-TOKEN\u003C\u002Fcode> as \u003Ccode>X-XSRF-TOKEN\u003C\u002Fcode>, keep cookies on. On Laravel 11\u002F12, do not exclude \u003Ccode>XSRF-TOKEN\u003C\u002Fcode> from cookie encryption. Confirm bad logins return 401, not 419.\u003C\u002Fp>\n\u003Ch3>Sanctum vs Passport for this issue?\u003C\u002Fh3>\n\u003Cp>This 419 path is about cookie-session CSRF for first-party SPAs — Sanctum’s model. Passport\u002FOAuth token APIs don’t use this XSRF cookie flow the same way. See \u003Ca href=\"\u002Fblog\u002Flaravel-sanctum-vs-passport\">Sanctum vs Passport\u003C\u002Fa> for which auth to pick.\u003C\u002Fp>\n\u003Ch3>Is excluding XSRF-TOKEN from encryption ever required?\u003C\u002Fh3>\n\u003Cp>Not for a normal Axios\u002Ffetch SPA that only copies the cookie into a header. Modern Laravel expects that cookie to be encrypted and the header to be decrypted.\u003C\u002Fp>\n\n\u003Ch2 id=\"summary\">Summary\u003C\u002Fh2>\n\u003Cp>If Sanctum SPA writes all 419, check whether \u003Ccode>XSRF-TOKEN\u003C\u002Fcode> was excluded from encryption. Laravel decrypts \u003Ccode>X-XSRF-TOKEN\u003C\u002Fcode>; plaintext cookies fail that step. Remove the exclusion, decode the cookie in the client, and use 401-vs-419 as your done check. For the wider Sanctum setup, see \u003Ca href=\"\u002Fblog\u002Flaravel-api-authentication\">Laravel Sanctum API authentication\u003C\u002Fa>.\u003C\u002Fp>\n\n\u003Ch2 id=\"key-takeaways\">Key Takeaways\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>419 means CSRF failed; 401 means the controller ran.\u003C\u002Fli>\n\u003Cli>Laravel decrypts \u003Ccode>X-XSRF-TOKEN\u003C\u002Fcode> — keep \u003Ccode>XSRF-TOKEN\u003C\u002Fcode> encrypted.\u003C\u002Fli>\n\u003Cli>The SPA should echo and decode the cookie, not “interpret” a plaintext token.\u003C\u002Fli>\n\u003Cli>Prove the fix with a bad-password login that returns 401.\u003C\u002Fli>\n\u003Cli>Separate origin\u002FHTTPS mistakes from CSRF encryption mistakes.\u003C\u002Fli>\n\u003C\u002Ful>","https:\u002F\u002Fik.imagekit.io\u002F93se7t7h4e\u002Fportfolio\u002Fposts\u002Fblog\u002Fcovers\u002F1792229994752-From-CSRF-Error-to-Secure-Fix_FIVIW5po2.webp","Laravel Sanctum 419 Fix — XSRF-TOKEN Encryption","Fix Laravel Sanctum 419 CSRF on SPA login: why encryptCookies(['XSRF-TOKEN']) breaks VerifyCsrfToken, how to prove it, and the one-line fix.","https:\u002F\u002Fik.imagekit.io\u002F93se7t7h4e\u002Fportfolio\u002Fposts\u002Fblog\u002Fog\u002F1792229989975-XSRF-Cookie-to-Secure-Token_kNPD6rMYf.webp",[19,20,21,22,23,24,25],"Laravel","Sanctum","CSRF","419","SPA","Nuxt","API Authentication","published","2026-10-17T09:40:04.212+00:00",17,null,"","2026-10-17T09:40:06.051151+00:00",[],[34,49,66,68,82,96,108,120,134,147,158,169,181,194,208,219,230,239,250,264,276,285,296,309],{"id":35,"title":36,"slug":37,"excerpt":38,"cover_image":39,"tags":40,"published_at":46,"updated_at":47,"view_count":48},"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",[41,42,43,44,45,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":50,"title":51,"slug":52,"excerpt":53,"cover_image":54,"tags":55,"published_at":63,"updated_at":64,"view_count":65},"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",[56,57,58,42,6,59,60,61,62],"nuxt","supabase","multi-tenancy","vue","pinia","vuetify","ai","2026-10-21T12:07:58.857+00:00","2026-10-21T12:07:59.070373+00:00",16,{"id":9,"title":10,"slug":11,"excerpt":12,"cover_image":14,"tags":67,"published_at":27,"updated_at":31,"view_count":28},[19,20,21,22,23,24,25],{"id":69,"title":70,"slug":71,"excerpt":72,"cover_image":73,"tags":74,"published_at":79,"updated_at":80,"view_count":81},"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",[24,75,76,77,78],"ImageKit","Vue","TypeScript","SEO","2026-10-17T05:55:24.556+00:00","2026-10-17T05:55:24.735773+00:00",23,{"id":83,"title":84,"slug":85,"excerpt":86,"cover_image":87,"tags":88,"published_at":94,"updated_at":95,"view_count":65},"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",[89,90,91,92,93],"Apache","Ubuntu","Installation","Linux","Web Server","2026-09-09T03:49:25.809+00:00","2026-09-09T03:49:26.679843+00:00",{"id":97,"title":98,"slug":99,"excerpt":100,"cover_image":101,"tags":102,"published_at":105,"updated_at":106,"view_count":107},"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",[89,103,90,93,92,104],"Nginx","DevOps","2026-09-04T12:14:08.218+00:00","2026-09-04T12:14:08.430018+00:00",9,{"id":109,"title":110,"slug":111,"excerpt":112,"cover_image":113,"tags":114,"published_at":117,"updated_at":118,"view_count":119},"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",[115,90,103,92,116,104],"Virtual Host","VPS","2026-09-04T12:09:22.623+00:00","2026-09-04T12:09:22.931401+00:00",12,{"id":121,"title":122,"slug":123,"excerpt":124,"cover_image":125,"tags":126,"published_at":131,"updated_at":132,"view_count":133},"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,127,128,129,130],"Queues","Jobs","PHP","backend","2026-08-21T04:36:56.222+00:00","2026-08-21T04:36:56.606735+00:00",20,{"id":135,"title":136,"slug":137,"excerpt":138,"cover_image":139,"tags":140,"published_at":144,"updated_at":145,"view_count":146},"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,141,142,143,129],"Eloquent","N+1","performance","2026-08-20T04:17:43.609+00:00","2026-08-20T05:50:24.297698+00:00",14,{"id":148,"title":149,"slug":150,"excerpt":151,"cover_image":152,"tags":153,"published_at":155,"updated_at":156,"view_count":157},"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,141,129,154,130],"ORM","2026-08-19T07:03:17.721+00:00","2026-08-20T04:19:08.829027+00:00",18,{"id":159,"title":160,"slug":161,"excerpt":162,"cover_image":163,"tags":164,"published_at":167,"updated_at":168,"view_count":65},"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.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1787114417893-hp3hmc.webp",[19,165,141,129,166],"Database","Transactions","2026-08-19T04:44:00.327+00:00","2026-08-19T05:14:18.190197+00:00",{"id":170,"title":171,"slug":172,"excerpt":173,"cover_image":174,"tags":175,"published_at":179,"updated_at":180,"view_count":146},"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,129,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,129,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":146},"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":157},"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",[24,189,215,216,76],"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":119},"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",[24,76,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":81},"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,20,25,129,23,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":157},"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,20,246,25,129,247,23],"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,129,77,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":119},"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",[77,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":146},"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":157},"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,20,292,293,23],"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,129,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":133},"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":30,"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,129,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,77,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,129,400,399,227,77,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,77],"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,77],"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,77,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"]