Question 1

What does Struktive actually do?

Accepted Answer

Struktive takes a messy CSV export of your data centre asset inventory and returns a clean, structured, scored version of that data — ready to import into any DCIM, ITSM, or CMDB platform. It normalises vendor names (resolving 40–80 raw variants down to 15–25 canonical names), parses free-text location strings into a structured hierarchy (Site → Building → Floor → Room → Row → Rack → U Position), classifies every asset into one of eight categories (Compute, Networking, Storage, Power, Cooling, Facilities, Out of Scope, Unknown), and scores each record 0–100 on data quality. The output is a six-sheet Compliance Audit Pack plus platform-specific export files for NetBox, dcTrack, Device42, or Struktive Native format.

Question 2

What file formats does Struktive accept?

Accepted Answer

Struktive accepts CSV and Excel files. It handles real-world exports — files with metadata preamble rows, inconsistent quoting, mixed delimiters, short rows, and empty rows are all handled gracefully. The pre-processor strips noise before normalisation begins. Maximum file size is 50 MB per upload.

Question 3

Do I need to format my CSV before uploading?

Accepted Answer

No. Struktive auto-detects column mappings using a library of 200+ header aliases (e.g. 'Cab Location', 'Cabinet', 'Rack', 'Asset Tag', 'Serial Number', 'S/N'). You do not need to rename columns or reformat your file before uploading. If a column cannot be mapped, it is passed through as-is.

Question 4

How does the quality score work?

Accepted Answer

Every record receives a 0–100 quality score based on seven weighted factors: field completeness (are the critical fields populated?), location depth (how many levels of the location hierarchy are resolved?), serial number validity (is it a real serial or a placeholder like 'TBD' or 'N/A'?), classification confidence (how certain is the category assignment?), vendor resolution (was the manufacturer name matched to a canonical form?), hostname/IP validity (does the hostname follow a real naming convention?), and duplicate risk (does this record share a serial or location with another record?). The score is a direct measure of import readiness.

Question 5

What is the Compliance Audit Pack?

Accepted Answer

The Compliance Audit Pack is a six-sheet XLSX file generated for every normalisation job. It contains: a Cover sheet with chain-of-custody metadata (source file SHA-256 hash, processing timestamp, normaliser version, record count, and sign-off blocks); an Asset Register with the full normalised inventory; an Audit Trail showing every field transformation; a Duplicates Register; an Exceptions Log; and a Summary Statistics sheet. Every pack is assigned a unique Pack ID and SHA-256 fingerprint stored in a tamper-evident record.

Question 6

What is re-ingestion and baseline diffing?

Accepted Answer

Re-ingestion is the process of uploading a new inventory export for a site that already has a prior normalised baseline. Struktive automatically detects the prior baseline, runs the new inventory through the same normalisation pipeline, and then diffs the two — classifying every asset as Added, Removed, Changed, Unchanged, or Score Changed. The result is a Change Report XLSX showing exactly what moved between the two snapshots.

Question 7

What types of data centres does Struktive support?

Accepted Answer

Struktive supports all five main data centre types: enterprise, colocation, hyperscale, edge, and modular. The normalisation engine resolves vendor names, classifies device roles, parses rack location strings, and scores data quality regardless of the source environment.

Question 8

Where is my data stored?

Accepted Answer

Uploaded files and generated exports are stored in an S3-compatible object store. Files are referenced by a non-enumerable key with a random suffix — they cannot be guessed or enumerated. Metadata is stored in a MySQL-compatible database. No data is shared with third parties.

Question 9

Can I delete my data?

Accepted Answer

Yes. You can delete individual jobs from your Job History page. Deleting a job removes the associated records, export files, and metadata from the system. Compliance Audit Packs are retained for 12 months from generation date as part of the tamper-evident audit trail.

Question 10

Does Struktive use my data to train models?

Accepted Answer

No. Your inventory data is never used to train machine learning models. The LLM receives only the asset description and category options — it does not receive your hostnames, serials, IP addresses, or location data.

Question 11

Is my data encrypted in transit and at rest?

Accepted Answer

Yes. All data is encrypted in transit via TLS 1.2+. Data at rest is encrypted using AES-256 at the storage layer. API keys are stored as SHA-256 hashes — the raw key is shown once at creation and never stored.

Question 12

Is Struktive SOC 2 compliant?

Accepted Answer

Struktive is on the path to SOC 2 Type II. The current implementation includes the key technical controls required: SHA-256 chain-of-custody on all exports, a tamper-evident audit pack registry with 12-month retention, field-level audit trails, role-based access control, and encrypted storage.

Question 13

What compliance frameworks does the Compliance Audit Pack support?

Accepted Answer

The Compliance Audit Pack supports evidence requirements for ISO 27001 (asset inventory controls), SOC 2 Type II (change management and data integrity), EU EED Annex I (power and capacity reporting), and internal audit processes. The Cover sheet includes sign-off blocks and a Methodology tab.

Question 14

How long are audit packs retained?

Accepted Answer

Compliance Audit Packs are retained for 12 months from the date of generation. This retention period is fixed and cannot be shortened.

Question 15

Which DCIM platforms does Struktive export to?

Accepted Answer

Struktive currently supports four export profiles: NetBox (slug-based CSV with DeviceType Library lookup), Sunbird dcTrack (XLSX with hierarchical location mapping), Device42 (three-row-header CSV), and Struktive Native (clean CSV with all normalised fields). The platform selector appears at download time.

Question 16

How does the NetBox export work?

Accepted Answer

The NetBox export generates a slug-based CSV where every manufacturer name, device type, site, rack, and role is converted to a NetBox-compatible slug. The export runs a pre-flight check against the NetBox DeviceType Library to identify any device types not in the library.

Question 17

Does Struktive support ServiceNow or Nlyte?

Accepted Answer

ServiceNow and Nlyte are on the integration roadmap. The Struktive Native CSV export is compatible with any platform that accepts a flat CSV import — you can use it as a starting point for ServiceNow CMDB imports with minor column remapping.

Question 18

How does Struktive pricing work?

Accepted Answer

Struktive uses a credit-based model. Credits are purchased in packs and consumed per record processed. There is a free tier that allows you to normalise up to 50 records without purchasing credits — no login required.

Question 19

What counts as a record?

Accepted Answer

One record is one row in your uploaded CSV file, after the pre-processor strips empty rows and metadata preamble rows.

Question 20

Do credits expire?

Accepted Answer

Credits do not expire. Once purchased, they remain in your account until used.

Question 21

Is there an enterprise plan?

Accepted Answer

Yes. Enterprise plans include volume pricing, dedicated support, custom export profiles, and SLA commitments. Contact us to discuss enterprise pricing.

Question 22

What happens to my uploaded file after processing?

Accepted Answer

Your original uploaded file is automatically deleted from our storage servers when your job completes. This happens without any action from you. We keep the normalised results — not your raw file.

Question 23

How long is my data retained?

Accepted Answer

Free-tier jobs (no account) are retained for 90 days. Paid jobs are retained for 12 months. Compliance Audit Packs are retained for 12 months regardless of tier. Data is purged automatically by a nightly cleanup job.

Question 24

Is my data used to train AI models?

Accepted Answer

No. Your inventory data is never used to train, fine-tune, or build datasets for any machine learning model. The LLM classification stage receives only the asset description and category options for each record.

Question 25

Can other users see my data?

Accepted Answer

No. Every job is isolated to your account or session. Authenticated jobs are accessible only to the account that created them. Anonymous jobs are accessible only via the unique job ID.

Question 26

What security controls are in place?

Accepted Answer

TLS 1.2+ on all connections. Security headers on every response (HSTS, X-Frame-Options: DENY, X-Content-Type-Options: nosniff). Rate limiting at three tiers. Passwords hashed with bcrypt. API keys stored as SHA-256 hashes.

Question 27

How are Compliance Audit Packs protected against tampering?

Accepted Answer

Every pack receives a SHA-256 hash at generation time stored in a tamper-evident registry with WORM semantics. Verify any pack at struktive.io/verify.

Question 28

Where can I read the full security documentation?

Accepted Answer

struktive.io/security covers the complete data lifecycle, all technical controls, data handling commitments, and responsible disclosure contact. A machine-readable security.txt is at /.well-known/security.txt.

Everything you need to know about Struktive

Product

Ready to clean your inventory?