Architecture
Module scopes, read-only data, premade report templates, and encrypted API keys under Integrations — never in the message box. How the workspace assistant stays honest.
Faith
As we begin our study of Paul's first letter to the church in Thessalonica, we learn some important history of the city, are reminded of Paul's experience there during one of his missionary journeys, and see how the cit…
Architecture
Part 7 of the inveazy tech series. How the template becomes a dedicated install after paid checkout — provision job, out-of-process worker, six deploy artifacts, and Subscribers — without cloud admin secrets in the web…
Faith
In 1 Thessalonians 1:9-10, Paul assures the church at Thessalonica that they have been delivered from the coming wrath. But just what is it, when is it coming, and how can we ensure we are spared as well? As we take a d…
Architecture
Part 6 of the inveazy tech series. How the same product moves from laptop Docker SQL to shared LAN catalogs to Azure customer sites — without treating any of those databases as disposable. CI/CD, config layers, and rele…
Architecture
Part 5 of the inveazy tech series. Soft tenancy leaks data across branches. When an operator switches warehouses, every hub query must already know which workspace — the browser never decides.
Architecture
Part 4 of the inveazy tech series. How hub screens stay maintainable: Razor layouts and partials, JavaScript that enhances the document against /api, and SQL that stays on the server.
Supply Chain
From the inveazy SCM theme. Small operations already run a supply chain — they just run it in five tools that disagree by Friday. How one catalog and posted documents replace the spreadsheet-and-cart stack.
Architecture
Part 3 of the inveazy tech series. How inveazy runs one ASP.NET Core host with two contracts: Razor for people, JSON under /api for hub scripts — and why a failed save must stay JSON so the composer is still the compose…
Architecture
How inveazy publishes schema with a dacpac and sqlpackage compare, gates sample seed, and locks down live Azure SQL and LAN catalogs so a product update does not reshuffle customer rows.
Architecture
Why inveazy treats the SQL Server database project as the schema contract: dacpac publish, gated seed, filtered indexes, row-level audit, and EF Core as a client of published SQL instead of the owner of DDL.
Architecture
How we built inveazy: a SQL Server dacpac as the schema contract, ASP.NET Core hubs and APIs on .NET 10, organization and workspace tenancy, Docker and Azure hosting, and paid provisioning to a customer site.
Supply Chain
Before you pay a vendor bill, prove the purchase order, the receipt, and the invoice agree — or know exactly why they don’t. Here’s how Purchasing, Receiving, Inventory, and AP each own a step.
How-to
How Countertop Point of Sale works for in-person sales, why we prefer Stripe Readers S700/S710, and how to configure the readers with the same commerce keys as the storefront and invoice pay links.
How-to
Three ways to sell on one set of rails: branded web storefront, desk quotes and sales orders, and Counter POS. Same customers, catalog, invoices, and Stripe — pick the channel that fits each sale.
Getting Started
Open inveazy.com and hvt.inveazy.com side by side and they barely look related—same platform, two guest stories. Here’s how Admin → Public site turns a SaaS home into your company website.
Getting Started
Part 9 of the how-to series: when to use mobile vs desktop SCM, receive / pick / put-away / ship scan modes, LPN staging, and practical barcode tips.
Getting Started
Part 8 of the how-to series: invoices, vendor bills, and the finance dashboard — plus Admin → Integrations for Stripe, QuickBooks, SMTP, AI keys, and optional read-only reporting.
Getting Started
Part 7 of the how-to series: compose and publish in Blog hub, use the workspace assistant with module scope, and open files, notifications, and calendar.
Getting Started
Part 6 of the how-to series: products, vendors, purchase and sales orders, warehouse receive and ship, plus the public store and web orders queue.
Getting Started
Part 5 of the how-to series: CRM organizations, accounts, contacts, and pipeline — plus PM projects and work items for delivery after the sale.
Getting Started
Part 4 of the how-to series: add people in User manager, assign roles, turn modules on for the workspace, and decide who can open which apps.
Getting Started
Part 3 of the how-to series: set My organization letterhead for documents, then Public site branding so visitors see your company — not a generic landing page.
Getting Started
Part 2 of the how-to series: choose a plan on Features & pricing, get your {slug}.inveazy.com site, create your first live organization, and set up your profile.
Getting Started
Part 1 of the how-to series: what inveazy is, who it helps, how you customize it, and the main areas of the product — CRM, supply chain, B2B storefront, accounting, and more.