FAQ
Answers for institutional decision-making.
Explore execution rights™, system boundaries, integration and evidence. These answers distinguish architecture principles from outcomes that must be verified for a specific deployment. For questions about your institution, contact access@immoquick.eu.
THE KEY QUESTIONS FIRST
Before the terminology: can your system answer these effect questions?
The detailed FAQ remain fully available below. For a faster entry, the most important architecture questions are now combined in a clear assessment — with visuals, explanations and a gap map instead of an artificial score.
Two systems. Clear architecture boundaries.
The immo.quick Serverless Edition™ uses no Trusted Execution Environments (TEEs) and no enclaves. TEE and enclave technologies are used exclusively in immo.quick Core™. The two products are independent systems. Core™ is not a prerequisite for the Serverless Edition™.
The Serverless Edition™ checks defined conditions at the integrated execution path and records the decision in cryptographically verifiable evidence. TEE attestation is not part of its architecture. Hardware-backed isolation and enclave attestation belong to the Core™ architecture profile.
🏛️ FUNDAMENTALS & CATEGORY
What exactly is immo.quick, and what is it not?
immo.quick is not compliance software in the classical sense, not a dashboard, not a GRC tool, not a reporting system. immo.quick is a deterministic execution infrastructure that establishes whether a valid right to execute exists and produces cryptographically verifiable evidence of that determination. The difference: classical systems document that something happened. immo.quick determines, deterministically, whether a given execution was permitted under the applicable rule state, and seals the result as evidence designed for judicial and regulatory review.
immo.quick Core™ →
Does immo.quick replace our existing compliance system?
No, immo.quick is an infrastructure layer, not an application layer. It complements existing systems by cryptographically sealing the domain determinations and execution decisions relevant to your process. Your existing GRC tool remains. immo.quick makes the underlying determination and its evidence independently verifiable.
Why wasn't this built earlier?
Several technologies had to mature and become practically deployable together: post-quantum cryptography (NIST standardized 2024), distributed deterministic execution and, exclusively for immo.quick Core™, trusted execution environments. The Serverless Edition™ is an independent system using no TEEs and no enclaves.
🔒 SECURITY & DATA SOVEREIGNTY
We use AWS. Does our data fall under the US CLOUD Act?
With immo.quick Core™, sensitive data and computations run in hardware-attested enclaves in the EU. The enclave operator has no access to plaintext data, physically, not just contractually. A lawful US disclosure request can still compel a cloud provider to produce whatever it holds. Where the provider holds neither plaintext nor sufficient key material, compelled production yields ciphertext, not intelligible customer data. immo.quick does not claim legal immunity from process, it claims a technical architecture designed to reduce what can be meaningfully produced.
Cloud Provider Section →
What happens when quantum computers break RSA-2048? Are our archives worthless?
Classical RSA-2048 signatures are understood to be vulnerable to a sufficiently capable quantum computer at some future point, current public estimates vary and are not something immo.quick asserts a precise date for. immo.quick's evidence architecture uses hybrid classical and post-quantum signatures (Ed25519 plus ML-DSA-87, NIST FIPS 204) so that historical evidence does not depend on a single classical assumption remaining unbroken.
Can immo.quick employees access our data?
No. Data in the TEE (Core™) is not readable by the system operator. No SSH, no console access, no API access to plaintext data. All administrative access is just-in-time, time-limited, approved and audited, and cannot reach TEE contents. This is an architectural property, not a policy promise.
⚖️ REGULATORY & LEGAL
Are immo.quick Warranty Tokens admissible in court?
Warranty Tokens are signed with Ed25519 and ML-DSA-87 and chained via SHA-384. A qualified RFC 3161 timestamp for the daily roots is built in but not yet in operation. This combination is designed to meet the evidentiary requirements of German law (ZPO §371a), EU law and the US Federal Rules of Evidence 901(b)(9). Whether a specific artifact is admitted as evidence in a specific proceeding remains a determination for the competent court, immo.quick does not certify admissibility.
How does immo.quick simultaneously resolve conflicts between GDPR and the CLOUD Act?
Through physical data placement rather than contractual assurances alone. Data processed in the EU enclave is intended to remain inaccessible in plaintext to a non-EU provider, reducing exposure to compelled disclosure of usable data. This is a technical mitigation, not a claim that GDPR and CLOUD Act obligations are legally resolved or that any party is immune from lawful process.
All jurisdiction conflicts →
Does immo.quick fulfill DORA Art. 5 for personal management liability?
immo.quick can help institutions maintain a cryptographically sealed, time-stamped record of the rule state, authority state and evidence relevant to an ICT-related execution decision, which can support the kind of documentation DORA Art. 5 governance expects. immo.quick does not calculate a liability score, does not determine insurance pricing, and does not claim any specific effect on D&O premiums. Those remain matters for the institution's own risk, legal and insurance functions.
🆕 NEW GATES & OWIG REFORM
Which gates were added most recently?
The Gate Catalog is extended as new regulatory domains require deterministic coverage. Recent additions span AI Act governance, digital infrastructure law, financial market infrastructure and asset management and securities financing. The current catalogue and category structure are maintained on the Gate Directory.
Is §30(2a) OWiG (new) already in force?
No. §30(2a) OWiG (new) is part of a government bill implementing EU Directive 2024/1203, still moving through the legislative process at the time of writing, with no confirmed entry-into-force date. The underlying EU directive has been adopted at EU level; national implementation is still pending. Related gate logic can be operated today to prepare for the foreseeable legal position, but this does not replace current legal advice.
What is SUB-GATE 5 at gateHeavyIndustry?
It performs a deterministic domain determination on defined conditions, such as permit validity and required pre-notification, before a batch release proceeds, rather than documenting a violation after the fact. A detected failure, such as an expired permit combined with a missing pre-notification, produces a domain-specific BLOCK result and a sealed evidence record.
What does SLE eligibility mean in practice?
A sealed receipt can carry a compliance_attestation.sle_eligible field set to true once the relevant deterministic execution-lock proof standard is met. This is a cryptographically verifiable signal to a regulator that the relevant condition was checked at the point of execution. It is not a guarantee of any specific fine reduction or regulatory outcome, that determination remains with the competent authority.
Why do gateCBDC and gateTaxExecution each have their own sub-gates instead of a shared one?
Each gate is scoped to a defined area of law. gateCBDC resolves pseudonymity and sanctions-related conditions before a ledger entry is touched, gateTaxExecution resolves VAT-related conditions at the point of sale. They do not share sub-gate logic because their underlying legal conditions are substantively unrelated, combining them would reduce the precision of the deterministic result for each.
How does gateBundID differ from the Gate 0 constitutional check?
Gate 0 on jurisdictions.html performs a cross-jurisdictional check on collisions between higher-order legal norms. gateBundID is a sector-specific gate that cryptographically binds a specific digital administrative act to a citizen's eIDAS eID assertion. Both operate at a foundational level within their own scope, but they are architecturally separate layers with different objects of determination.
⚙️ TECHNICAL & INTEGRATION
How long does a complete compliance check take?
Individual gate evaluations typically complete in well under a second. A full multi-gate pipeline, covering identity resolution, sanctions and source checks, jurisdiction determination, applicable-framework resolution and evidence sealing, is designed to complete within single-digit seconds for most institutional workloads. Actual latency depends on the specific pipeline, source availability and deployment configuration.
How is immo.quick integrated into existing systems?
Via two routes: immo.quick Core™ for institutional deployments requiring dedicated sovereign infrastructure and hardware attestation, and the immo.quick Serverless Edition™ for API-first integration. Both routes produce the same class of sealed, independently verifiable evidence artifacts. Integration timelines depend on institutional scope, governance requirements and the number of systems involved, and are agreed individually rather than promised as a fixed number of weeks.
Serverless Edition™ →
Can immo.quick be operated in an air-gap environment without internet connection?
The Serverless Edition™'s core™ determination logic does not require a live external network connection once the relevant rule states and source snapshots are provisioned locally. This can support deployment in controlled or air-gapped environments. Authoritative source updates and public verifiability naturally depend on eventual connectivity for refreshing that state.
What happens if immo.quick ceases to exist? Are our artifacts still usable?
Warranty Tokens and sealed receipts are issued in a long-term, self-contained signature format designed so the information needed for later verification is embedded in the artifact itself. The associated cryptographic signatures can be independently verified using open, published verification methods, not exclusively through immo.quick's own systems. This is a design goal for artifact longevity, not a guarantee against every possible future verification obstacle.
💼 BUSINESS & ACCESS
Who is immo.quick suitable for, and who is it not?
Suitable for: Regulated financial institutions, central banks, PE funds, insurance companies, FinTechs with regulatory requirements, governments and critical infrastructure, and institutional real estate investors.
Less suitable for: Unregulated companies without compliance requirements, or organizations looking primarily for a reporting dashboard rather than deterministic execution infrastructure.
Less suitable for: Unregulated companies without compliance requirements, or organizations looking primarily for a reporting dashboard rather than deterministic execution infrastructure.
How do I get access to immo.quick?
immo.quick is not a self-service product. Access is through an institutional access conversation, either for a technical deep-dive or a strategic board briefing. Inquiries exclusively via access@immoquick.eu. We respond within 48 hours.
What is Machine Law™, the book?
Machine Law™ is a reference work describing the doctrine behind immo.quick's architecture. It is intended as a technical and conceptual reference for institutions, regulators and legal teams evaluating the system, not as a promotional document.
Machine Law™, the Book →
YOUR QUESTION NOT LISTED?
We answer directly.
For technical questions, strategic discussions and institutional inquiries.
Ask a question →