<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Fundsroom Tech</title>
    <description>The latest articles on DEV Community by Fundsroom Tech (@fundsroom_tech_82070fdbc3).</description>
    <link>https://dev.to/fundsroom_tech_82070fdbc3</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4154648%2F81265c40-4346-41ac-8f24-b855269237a3.png</url>
      <title>DEV Community: Fundsroom Tech</title>
      <link>https://dev.to/fundsroom_tech_82070fdbc3</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/fundsroom_tech_82070fdbc3"/>
    <language>en</language>
    <item>
      <title>Designing a Manufacturing ERP: Connecting Sales, Inventory, Production, and Accounts</title>
      <dc:creator>Fundsroom Tech</dc:creator>
      <pubDate>Mon, 02 Nov 2026 07:02:00 +0000</pubDate>
      <link>https://dev.to/fundsroom_tech_82070fdbc3/designing-a-manufacturing-erp-connecting-sales-inventory-production-and-accounts-feg</link>
      <guid>https://dev.to/fundsroom_tech_82070fdbc3/designing-a-manufacturing-erp-connecting-sales-inventory-production-and-accounts-feg</guid>
      <description>&lt;p&gt;Exploring the architecture and workflows behind an integrated ERP solution for an earthing products manufacturer.&lt;/p&gt;

&lt;p&gt;Manufacturing software is not simply about managing inventory or generating reports. It involves connecting multiple business processes that depend on one another.&lt;/p&gt;

&lt;p&gt;A customer order can trigger procurement requirements. Procurement affects material availability. Material availability influences production planning. Production connects with project execution, delivery, and invoicing.&lt;/p&gt;

&lt;p&gt;When these activities operate independently, maintaining consistent information across departments becomes challenging.&lt;/p&gt;

&lt;p&gt;In this article, we'll explore how a manufacturing ERP solution can bring these processes together, using an earthing products manufacturer as a practical case study.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Understanding the Business Requirements&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Before designing the system, it is important to understand the operational requirements.&lt;/p&gt;

&lt;p&gt;An earthing products manufacturer may manage different products, components, materials, vendors, customer orders, and production activities.&lt;/p&gt;

&lt;p&gt;The ERP solution needs to support six major functional areas:&lt;/p&gt;

&lt;p&gt;Sales, quotations, and orders&lt;/p&gt;

&lt;p&gt;Vendor and material management&lt;/p&gt;

&lt;p&gt;Product engineering, BOM, and drawings&lt;/p&gt;

&lt;p&gt;Work orders and quality control&lt;/p&gt;

&lt;p&gt;Projects and service operations&lt;/p&gt;

&lt;p&gt;Accounts and profitability&lt;/p&gt;

&lt;p&gt;These modules represent different responsibilities, but they must work together through connected business workflows.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Designing a Modular ERP Structure&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;A modular architecture helps organize business functionality into manageable sections.&lt;/p&gt;

&lt;p&gt;Module 1: Sales and Order Management&lt;/p&gt;

&lt;p&gt;This module handles the customer-facing workflow:&lt;/p&gt;

&lt;p&gt;Lead management&lt;/p&gt;

&lt;p&gt;Quotation creation&lt;/p&gt;

&lt;p&gt;Customer order management&lt;/p&gt;

&lt;p&gt;Order tracking&lt;/p&gt;

&lt;p&gt;The sales process creates the initial business record that subsequent modules can reference.&lt;/p&gt;

&lt;p&gt;Module 2: Procurement and Inventory&lt;/p&gt;

&lt;p&gt;This module manages the movement and availability of materials.&lt;/p&gt;

&lt;p&gt;Core functionality includes:&lt;/p&gt;

&lt;p&gt;Vendor management&lt;/p&gt;

&lt;p&gt;Purchase management&lt;/p&gt;

&lt;p&gt;Inventory records&lt;/p&gt;

&lt;p&gt;Stock visibility&lt;/p&gt;

&lt;p&gt;The objective is to connect purchasing activities with inventory information.&lt;/p&gt;

&lt;p&gt;Module 3: Product Engineering&lt;/p&gt;

&lt;p&gt;Engineering information needs to be connected with manufacturing requirements.&lt;/p&gt;

&lt;p&gt;This module includes:&lt;/p&gt;

&lt;p&gt;Product master&lt;/p&gt;

&lt;p&gt;Bill of Materials (BOM)&lt;/p&gt;

&lt;p&gt;Product costing&lt;/p&gt;

&lt;p&gt;Engineering drawings&lt;/p&gt;

&lt;p&gt;The BOM provides a structured representation of the materials required for a product.&lt;/p&gt;

&lt;p&gt;Module 4: Production and Quality Control&lt;/p&gt;

&lt;p&gt;Production operations require visibility into work orders and inspection activities.&lt;/p&gt;

&lt;p&gt;The module includes:&lt;/p&gt;

&lt;p&gt;Work order management&lt;/p&gt;

&lt;p&gt;Production task tracking&lt;/p&gt;

&lt;p&gt;Quality inspection&lt;/p&gt;

&lt;p&gt;Production records&lt;/p&gt;

&lt;p&gt;This creates a structured relationship between manufacturing activities and their associated records.&lt;/p&gt;

&lt;p&gt;Module 5: Project and Service Management&lt;/p&gt;

&lt;p&gt;Some manufacturing orders also involve project execution and service-related activities.&lt;/p&gt;

&lt;p&gt;This module provides functionality for project records, service operations, and project tracking.&lt;/p&gt;

&lt;p&gt;Module 6: Accounts and Profitability&lt;/p&gt;

&lt;p&gt;The financial module connects business transactions with accounting and profitability information.&lt;/p&gt;

&lt;p&gt;It includes accounts, payment records, and profitability tracking.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Connecting Modules Through a Common Workflow&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;One of the most important aspects of ERP development is connecting modules through a consistent workflow.&lt;/p&gt;

&lt;p&gt;Consider a manufacturing job that starts with a customer enquiry.&lt;/p&gt;

&lt;p&gt;The process can be represented as:&lt;/p&gt;

&lt;p&gt;Customer Enquiry&lt;br&gt;
       |&lt;br&gt;
       v&lt;br&gt;
    Quotation&lt;br&gt;
       |&lt;br&gt;
       v&lt;br&gt;
  Order Confirmation&lt;br&gt;
       |&lt;br&gt;
       v&lt;br&gt;
   Procurement&lt;br&gt;
       |&lt;br&gt;
       v&lt;br&gt;
   Engineering&lt;br&gt;
       |&lt;br&gt;
       v&lt;br&gt;
    Production&lt;br&gt;
       |&lt;br&gt;
       v&lt;br&gt;
     Project&lt;br&gt;
       |&lt;br&gt;
       v&lt;br&gt;
     Invoice&lt;/p&gt;

&lt;p&gt;Each stage generates information that supports the next activity.&lt;/p&gt;

&lt;p&gt;For example:&lt;/p&gt;

&lt;p&gt;Sales creates the customer order.&lt;/p&gt;

&lt;p&gt;Procurement manages the required materials.&lt;/p&gt;

&lt;p&gt;Engineering provides product specifications and BOM information.&lt;/p&gt;

&lt;p&gt;Production manages work orders and quality activities.&lt;/p&gt;

&lt;p&gt;Project management tracks relevant execution activities.&lt;/p&gt;

&lt;p&gt;Accounts handles the financial records.&lt;/p&gt;

&lt;p&gt;This connected workflow helps establish a common operational view.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Inventory Management and RFID Integration&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Inventory tracking becomes particularly important in manufacturing environments.&lt;/p&gt;

&lt;p&gt;Businesses need to understand:&lt;/p&gt;

&lt;p&gt;On-hand stock&lt;/p&gt;

&lt;p&gt;Reserved stock&lt;/p&gt;

&lt;p&gt;Available stock&lt;/p&gt;

&lt;p&gt;Reorder requirements&lt;/p&gt;

&lt;p&gt;Store locations&lt;/p&gt;

&lt;p&gt;Batch information&lt;/p&gt;

&lt;p&gt;RFID can extend inventory management by connecting physical tags and readers with digital records.&lt;/p&gt;

&lt;p&gt;A simplified integration workflow looks like this:&lt;/p&gt;

&lt;p&gt;RFID Tag&lt;br&gt;
    |&lt;br&gt;
    v&lt;br&gt;
RFID Reader&lt;br&gt;
    |&lt;br&gt;
    v&lt;br&gt;
ERP Integration&lt;br&gt;
    |&lt;br&gt;
    v&lt;br&gt;
Inventory Record Update&lt;br&gt;
    |&lt;br&gt;
    v&lt;br&gt;
Batch and Stock Visibility&lt;/p&gt;

&lt;p&gt;When a tagged batch is scanned, the integration can process the identification data and update the relevant inventory record according to the configured business rules.&lt;/p&gt;

&lt;p&gt;Developers implementing this functionality should consider:&lt;/p&gt;

&lt;p&gt;Unique tag identification&lt;/p&gt;

&lt;p&gt;Duplicate scan handling&lt;/p&gt;

&lt;p&gt;Reader connectivity&lt;/p&gt;

&lt;p&gt;Transaction validation&lt;/p&gt;

&lt;p&gt;Inventory reconciliation&lt;/p&gt;

&lt;p&gt;Error handling&lt;/p&gt;

&lt;p&gt;Audit logs&lt;/p&gt;

&lt;p&gt;RFID integration should not be treated as simply connecting a scanner to a database. The physical inventory process and the digital transaction workflow must be designed together.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Why Data Consistency Matters&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;An integrated ERP system depends on reliable information shared across modules.&lt;/p&gt;

&lt;p&gt;For example, when a customer order requires a particular material, procurement and inventory need to reference the correct product and material records.&lt;/p&gt;

&lt;p&gt;Similarly, production activities should be associated with the appropriate work orders and product information.&lt;/p&gt;

&lt;p&gt;Some important development considerations include:&lt;/p&gt;

&lt;p&gt;Consistent master data across modules&lt;/p&gt;

&lt;p&gt;Proper record relationships&lt;/p&gt;

&lt;p&gt;Transaction validation&lt;/p&gt;

&lt;p&gt;Role-based access&lt;/p&gt;

&lt;p&gt;Audit trails&lt;/p&gt;

&lt;p&gt;Error handling&lt;/p&gt;

&lt;p&gt;Reliable reporting&lt;/p&gt;

&lt;p&gt;These considerations help make the system more maintainable as additional modules and workflows are introduced.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Building Dashboards Around Operational Data&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;A manufacturing ERP dashboard should provide a consolidated view of important business information.&lt;/p&gt;

&lt;p&gt;Depending on the implemented modules, management may need visibility into:&lt;/p&gt;

&lt;p&gt;Sales and customer orders&lt;/p&gt;

&lt;p&gt;Purchasing and inventory&lt;/p&gt;

&lt;p&gt;Engineering records&lt;/p&gt;

&lt;p&gt;Work orders&lt;/p&gt;

&lt;p&gt;Production activities&lt;/p&gt;

&lt;p&gt;Projects&lt;/p&gt;

&lt;p&gt;Accounts and profitability&lt;/p&gt;

&lt;p&gt;The objective is to make operational information accessible without requiring management to navigate multiple disconnected systems.&lt;/p&gt;

&lt;p&gt;A useful dashboard should answer business questions rather than simply display charts.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Lessons From This ERP Case Study&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;While designing a manufacturing ERP solution, several important principles become clear:&lt;/p&gt;

&lt;p&gt;Understand the workflow before developing features.&lt;/p&gt;

&lt;p&gt;The system should reflect the actual sequence of business activities.&lt;/p&gt;

&lt;p&gt;Keep modules connected.&lt;/p&gt;

&lt;p&gt;Independent modules are useful only when they can exchange the information required by the business.&lt;/p&gt;

&lt;p&gt;Design for operational visibility.&lt;/p&gt;

&lt;p&gt;Users should be able to understand the status of orders, materials, and production activities.&lt;/p&gt;

&lt;p&gt;Consider integrations early.&lt;/p&gt;

&lt;p&gt;RFID and other external integrations should be considered during workflow and architecture planning.&lt;/p&gt;

&lt;p&gt;Build for evolving requirements.&lt;/p&gt;

&lt;p&gt;Manufacturing processes can change. The ERP should be structured to support future enhancements without unnecessarily complicating existing workflows.&lt;/p&gt;

&lt;p&gt;Conclusion&lt;/p&gt;

&lt;p&gt;Building manufacturing ERP software requires more than developing individual modules.&lt;/p&gt;

&lt;p&gt;The real engineering challenge is connecting sales, procurement, inventory, engineering, production, projects, and accounts into a consistent operational system.&lt;/p&gt;

&lt;p&gt;Our earthing products ERP case study at Fundsroom demonstrates this workflow-driven approach.&lt;/p&gt;

&lt;p&gt;We believe that effective business software starts with understanding how an organization works and then designing technology around those processes.&lt;/p&gt;

&lt;p&gt;Don't just build modules. Build connected business workflows.&lt;/p&gt;

&lt;p&gt;If you are exploring ERP development, manufacturing automation, or customized business software, connect with our team.&lt;/p&gt;

&lt;p&gt;Website: &lt;a href="https://fundsroomprojects.com/" rel="noopener noreferrer"&gt;https://fundsroomprojects.com/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Email: &lt;a href="mailto:business@fundsroom.com"&gt;business@fundsroom.com&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Fundsroom — Tech for All.&lt;/p&gt;

</description>
      <category>erp</category>
      <category>architecture</category>
      <category>manufacturing</category>
      <category>ai</category>
    </item>
    <item>
      <title>Beyond Features: Building Workflow-Driven Software with EduRoom and ERP</title>
      <dc:creator>Fundsroom Tech</dc:creator>
      <pubDate>Thu, 29 Oct 2026 05:55:13 +0000</pubDate>
      <link>https://dev.to/fundsroom_tech_82070fdbc3/beyond-features-building-workflow-driven-software-with-eduroom-and-erp-521g</link>
      <guid>https://dev.to/fundsroom_tech_82070fdbc3/beyond-features-building-workflow-driven-software-with-eduroom-and-erp-521g</guid>
      <description>&lt;p&gt;In software development, it is easy to focus on features, dashboards, and integrations. But building useful software starts with understanding the workflow behind the problem.&lt;/p&gt;

&lt;p&gt;At Fundsroom, we apply this principle across different solutions, including EduRoom and ERP inventory management.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;EduRoom: Structuring the Learning Workflow&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;EduRoom connects multiple stages of an internship program:&lt;/p&gt;

&lt;p&gt;Training sessions&lt;/p&gt;

&lt;p&gt;Student evaluation through FundsAI&lt;/p&gt;

&lt;p&gt;Real business tasks&lt;/p&gt;

&lt;p&gt;Completion tracking and certification&lt;/p&gt;

&lt;p&gt;Instead of managing each activity separately, the workflow brings the learning process together in a structured way.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;ERP: Connecting Inventory Operations&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Inventory management involves more than recording stock quantities. Businesses need visibility into available stock, reserved inventory, batches, storage locations, and reorder requirements.&lt;/p&gt;

&lt;p&gt;An ERP workflow can connect these operations:&lt;/p&gt;

&lt;p&gt;Receive Stock → Record Inventory → Track Batches → Update Availability → Monitor Reorders&lt;/p&gt;

&lt;p&gt;RFID can extend this workflow by connecting physical tags and reader scans with digital inventory records, when integrated with the ERP system.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;The Engineering Principle: Design the Workflow First&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Before choosing features or implementation details, developers should ask:&lt;/p&gt;

&lt;p&gt;What triggers the workflow?&lt;/p&gt;

&lt;p&gt;Who is responsible for each step?&lt;/p&gt;

&lt;p&gt;What data needs to be captured?&lt;/p&gt;

&lt;p&gt;How should errors and exceptions be handled?&lt;/p&gt;

&lt;p&gt;What information should be visible to users?&lt;/p&gt;

&lt;p&gt;Answering these questions helps developers design systems around actual operational needs rather than adding features without a clear purpose.&lt;/p&gt;

&lt;p&gt;Conclusion&lt;/p&gt;

&lt;p&gt;EduRoom and ERP inventory management solve different problems, but they share the same design principle: connect individual actions into a meaningful workflow.&lt;/p&gt;

&lt;p&gt;Good software is not just about what users can click. It is about helping them complete work accurately, consistently, and efficiently.&lt;/p&gt;

&lt;p&gt;At Fundsroom, we believe in building technology around real workflows.&lt;/p&gt;

&lt;p&gt;Explore our projects: &lt;a href="https://fundsroomprojects.com/" rel="noopener noreferrer"&gt;https://fundsroomprojects.com/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;What do you prioritize when designing software: features first, or workflows first?&lt;/p&gt;

</description>
      <category>productivity</category>
      <category>javascript</category>
      <category>programming</category>
      <category>ai</category>
    </item>
    <item>
      <title>Running a Multi-Tenant Platform on EC2: Node.js, PostgreSQL, SES and the AWS Cost Bug We Almost Missed</title>
      <dc:creator>Fundsroom Tech</dc:creator>
      <pubDate>Thu, 01 Oct 2026 11:54:30 +0000</pubDate>
      <link>https://dev.to/fundsroom_tech_82070fdbc3/running-a-multi-tenant-platform-on-ec2-nodejs-postgresql-ses-and-the-aws-cost-bug-we-almost-jgo</link>
      <guid>https://dev.to/fundsroom_tech_82070fdbc3/running-a-multi-tenant-platform-on-ec2-nodejs-postgresql-ses-and-the-aws-cost-bug-we-almost-jgo</guid>
      <description>&lt;p&gt;description: Real architecture notes from FundsWeb and FundsAudit: Express, Sequelize, PM2, Nginx, SES, S3 and a cross-region data transfer bill that taught us to read AWS cost reports.&lt;br&gt;
tags: aws, node, postgres, architecture&lt;br&gt;
canonical_url: &lt;a href="https://fundsroomprojects.com/blog/multi-tenant-platform-ec2-node-postgres" rel="noopener noreferrer"&gt;https://fundsroomprojects.com/blog/multi-tenant-platform-ec2-node-postgres&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  cover_image:
&lt;/h2&gt;

&lt;p&gt;We build and run &lt;a href="https://fundsweb.in" rel="noopener noreferrer"&gt;FundsWeb&lt;/a&gt;, a multi-tenant web platform, along with [FundsAudit] and an internal email validation service. This post covers the stack, the decisions we'd make again, and one AWS billing issue that cost us more than it should have.&lt;/p&gt;

&lt;h2&gt;
  
  
  The stack
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Layer&lt;/th&gt;
&lt;th&gt;Choice&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Runtime and API&lt;/td&gt;
&lt;td&gt;Node.js with Express&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Database&lt;/td&gt;
&lt;td&gt;PostgreSQL, installed directly on EC2&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;ORM&lt;/td&gt;
&lt;td&gt;Sequelize&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Process manager&lt;/td&gt;
&lt;td&gt;PM2&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Reverse proxy&lt;/td&gt;
&lt;td&gt;Nginx&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Email&lt;/td&gt;
&lt;td&gt;AWS SES&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Storage&lt;/td&gt;
&lt;td&gt;S3&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;DNS&lt;/td&gt;
&lt;td&gt;Route 53&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;PDF and document generation&lt;/td&gt;
&lt;td&gt;Puppeteer&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;It is deliberately plain. For a small team, fewer moving parts means faster debugging.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Why EC2 with PM2 and Nginx
&lt;/h2&gt;

&lt;p&gt;We run the app on EC2 instead of a managed container platform.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;PM2&lt;/strong&gt; restarts crashed processes, manages logs and gives us zero-downtime reloads with &lt;code&gt;pm2 reload&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Nginx&lt;/strong&gt; terminates TLS, serves static files, and proxies to the Node process. Each tenant domain is a server block pointing to the same app.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Trade-off:&lt;/strong&gt; we own patching, backups and scaling. Managed services remove that work. We chose control and predictable cost, and we accept the operational load.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  2. Tenancy with Sequelize
&lt;/h2&gt;

&lt;p&gt;Tenant context is resolved once per request and passed to the data layer, not rebuilt inside each controller.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Models include a tenant identifier, and scoped queries apply it centrally.&lt;/li&gt;
&lt;li&gt;Sequelize scopes keep the filter in one place, so a developer can't forget it on a single route.&lt;/li&gt;
&lt;li&gt;Migrations are versioned and run per environment.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;[Add one real detail: how you resolve the tenant (subdomain, domain, token) and one bug this design prevented.]&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Generating documents with Puppeteer
&lt;/h2&gt;

&lt;p&gt;We use Puppeteer to render HTML templates into PDFs for [reports / audit documents, edit to match].&lt;/p&gt;

&lt;p&gt;What we learned:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Treat the browser like any other heavy dependency: limit concurrency, set timeouts, and always close pages.&lt;/li&gt;
&lt;li&gt;Render from the same HTML templates the UI uses, so layout stays consistent.&lt;/li&gt;
&lt;li&gt;Memory spikes appear when many PDFs are queued at once, so queue them.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  4. Email on SES, and building FundsMailer
&lt;/h2&gt;

&lt;p&gt;Sending email through SES is easy. Keeping your sender reputation healthy is the hard part. Bounces and complaints affect delivery, so we built &lt;strong&gt;FundsMailer&lt;/strong&gt;, an internal email validation service.&lt;/p&gt;

&lt;p&gt;It checks addresses before sending, runs a set of validation checks, produces a score, and exposes the result through an API.&lt;/p&gt;

&lt;p&gt;One limitation worth knowing: probing mail servers over SMTP from EC2 has constraints, because AWS restricts outbound port 25 by default. So SMTP-level checks can't be the only signal. [Add which checks you rely on instead: syntax, DNS/MX, disposable-domain lists, etc.]&lt;/p&gt;

&lt;h2&gt;
  
  
  5. The cross-region bill
&lt;/h2&gt;

&lt;p&gt;This was the most useful lesson.&lt;/p&gt;

&lt;p&gt;Our EC2 instance and SES were in &lt;code&gt;us-east-1&lt;/code&gt;, but the S3 buckets used by the email pipeline were in &lt;code&gt;ap-south-1&lt;/code&gt;. Every read and write crossed regions, and AWS charges for inter-region data transfer. The cost showed up in billing before it showed up in any monitoring.&lt;/p&gt;

&lt;p&gt;What we did:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Used Cost Explorer, grouped by usage type, to find the data transfer line items.&lt;/li&gt;
&lt;li&gt;Traced them to the services moving data between regions.&lt;/li&gt;
&lt;li&gt;Created a new bucket in &lt;code&gt;us-east-1&lt;/code&gt;, next to SES and EC2, and migrated the pipeline to it.&lt;/li&gt;
&lt;li&gt;Repeated the same setup in our second AWS account.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;[Add the real before/after cost figure if you're comfortable sharing it, or say "a significant share of the bill".]&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Rule we follow now:&lt;/strong&gt; keep compute, email and storage in the same region unless there's a reason not to, and check the cost report by usage type every month.&lt;/p&gt;

&lt;h2&gt;
  
  
  6. Don't leave a bucket public by accident
&lt;/h2&gt;

&lt;p&gt;While auditing, we found a bucket serving images that was publicly writable or listable more than it needed to be. [Edit to match what you actually found.] We fixed it by turning on Block Public Access and serving public images through a controlled path.&lt;/p&gt;

&lt;p&gt;Review your bucket policies and ACLs on a schedule. It takes ten minutes and prevents long incidents.&lt;/p&gt;

&lt;h2&gt;
  
  
  7. FundsAudit: what's different
&lt;/h2&gt;

&lt;p&gt;[Write 4-6 real lines: what FundsAudit does, which part of the stack it leans on (for example Puppeteer reports, role-based access, audit trails), and one design decision you'd defend.]&lt;/p&gt;

&lt;h2&gt;
  
  
  What we'd tell a team starting today
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Keep the stack boring until a real constraint forces a change.&lt;/li&gt;
&lt;li&gt;Resolve tenant context in one place.&lt;/li&gt;
&lt;li&gt;Queue anything heavy, like PDFs or email sends.&lt;/li&gt;
&lt;li&gt;Keep compute, storage and email in one region.&lt;/li&gt;
&lt;li&gt;Read the AWS cost report by usage type every month.&lt;/li&gt;
&lt;li&gt;Audit bucket policies regularly.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;We build custom ERP and SaaS products at &lt;a href="https://fundsroomprojects.com" rel="noopener noreferrer"&gt;Fundsroom&lt;/a&gt;. If you're solving similar problems, tell us in the comments what you'd do differently.&lt;/p&gt;

</description>
      <category>aws</category>
      <category>node</category>
      <category>postgres</category>
      <category>architecture</category>
    </item>
  </channel>
</rss>
