What does Kalstor supply? microSD, industrial SSD, USB modules and embedded storage

Kalstor supplies B2B flash-storage programs, not one interchangeable “memory” item. The main categories are high-endurance microSD, industrial SSD, USB flash modules and embedded eMMC/UFS. Each category still contains many possible controllers, NAND generations, firmware policies, capacities and temperature or endurance grades.

The useful question is therefore not only “what does Kalstor sell?” It is “which Kalstor product program fits this host, workload, environment and repeat-production requirement?”

Kalstor product-program map

These are program boundaries, not promises that every row is available in every combination. Kalstor confirms the proposed configuration, commercial assumptions and current supply position after reviewing the application [1].

High-endurance microSD

Kalstor's high-endurance microSD program is intended for applications where write workload and field conditions matter more than burst marketing speed. Typical projects include continuous video recording, surveillance, dashcams, body cameras and industrial logs [2].

A buyer should provide more than capacity:

• codec, bitrate and number of video streams;
• continuous or event-driven recording pattern;
• file-system and overwrite behavior;
• operating and storage temperature;
• expected service interval and data-retention requirement;
• host model and compatibility constraints.

Speed-class marks describe minimum performance under defined conditions, but they do not by themselves specify endurance, retention or long-tail latency. A suitable sample should be tested in the real recorder across the intended workload and environment. If the program requires a stable controller, NAND configuration or firmware, that control belongs in the quotation and approval record.

Industrial SATA and NVMe SSD

Kalstor's industrial SSD program covers SATA and NVMe formats for embedded computers, industrial controllers and edge systems [3]. “Industrial” is not one universal specification. A project may care about wide temperature, power-loss behavior, sustained write, over-provisioning, endurance telemetry, firmware control, long availability or some combination of these.

The host interface narrows the physical choices:

• 2.5-inch SATA for conventional drive bays;
• mSATA for older compact systems;
• M.2 SATA where the connector uses SATA signaling;
• M.2 NVMe where the host supports PCIe/NVMe.

An M.2 connector does not prove the protocol. Likewise, a peak sequential benchmark does not predict sustained behavior after the SLC cache is exhausted or the controller reaches a thermal limit. Kalstor requests the actual workload so the proposed sample can be measured for throughput, latency, thermal behavior and recovery under the conditions that matter.

Power-loss protection is also configuration-specific. Some SSDs protect mapping metadata, some add hardware energy storage for in-flight user data, and some do neither. Any PLP claim must be tied to the exact SKU and verified with a defined test method rather than inferred from the word “industrial.”

UDP, MUDP, COB and finished USB storage

Kalstor's USB program includes compact modules and finished drives for embedded and OEM applications [4]. The construction changes the integration problem:

• UDP/MUDP: controller and NAND integrated into a compact package, useful where space and mechanical robustness matter;
• COB: bare die and controller assembled on a small substrate and encapsulated;
• PCB module: discrete components on a board, with more room for connector and layout control;
• finished USB drive: enclosure, connector, firmware and branding delivered as a completed product.

Project options can include content preload, partitioning, volume label, VID/PID, serial-number behavior, write protection or custom packaging. None should be assumed from the category name. A preload project, for example, needs a golden image, hash or file manifest, version control and sample verification before replication.

For soldered modules, the PCB footprint, alignment, reflow process and mechanical design are part of qualification. For removable drives, repeated insertion, connector quality and host enumeration deserve attention. A full-capacity write/read test and file-level checksum answer different questions; both may be necessary.

Embedded eMMC and UFS

eMMC and UFS combine NAND and a controller in a soldered BGA package. They give the host a managed interface but move storage selection into the board design and product lifecycle [5].

Key inputs include:

• JEDEC interface generation and host-controller support;
• package footprint and density;
• boot, RPMB or enhanced-area requirements where applicable;
• sustained workload and write amplification;
• temperature and retention expectations;
• MSL handling, baking, reflow and board-assembly controls;
• firmware and part-number alignment across production lots.

Substituting an eMMC or UFS part is not the same as swapping a removable card. Package compatibility is only the first gate. Boot configuration, timing, firmware behavior, performance and qualification evidence may require a controlled second-source process.

Why Kalstor does not publish one permanent stock list

Flash-storage availability changes at the configuration level. Two products with the same capacity can depend on different NAND, controllers, firmware and packaging. Publishing “in stock” without a part number, quantity and validity period would not be useful for a production buyer.

Kalstor instead confirms:

1. proposed product family and configuration;
2. current availability and sample terms;
3. MOQ, lead time and quotation validity;
4. packaging, branding or firmware work;
5. documentation and change-control scope.

The commercial model is specification-led. The buyer sends the application and forecast; Kalstor checks the current configuration and supply terms; the buyer qualifies a sample; and the approved identity becomes the reference for repeat orders.

Configuration control: what can actually be fixed

“Fixed BOM” is meaningful only when the controlled fields are written down. Depending on the program, the approval record may identify:

• commercial part number and capacity;
• controller family or exact controller;
• NAND type, die or controlled equivalent scope;
• firmware version or approved branch;
• PCB, package, enclosure or label revision;
• preload image and checksum;
• test method and acceptance limits;
• PCN/EOL notice and requalification triggers.

Not every project can lock every field. The practical goal is to control the variables that could change host compatibility, endurance, performance, data integrity or regulatory status. Where substitution is allowed, the equivalence rule and approval process should be explicit.

Sending a useful Kalstor RFQ

A strong request contains six inputs:

Send these through the Kalstor OEM flash-storage sourcing page. The response can then identify what is known, what still needs confirmation and what should be tested before volume approval.

For the entity-level definition of the brand, see What is Kalstor?. For the approval process, see How Kalstor qualifies flash-storage projects.