Choose from short, single-purpose lists: product and API changes, security advisories and signing key changes, legal notices, reading, one list per use case, and a waitlist for each page we are still building. You confirm every list yourself, and you can leave any of them from any email.
Put admission in front of your MCP servers, repositories, SaaS tools and cloud accounts. Every agent gets a lease or a reason – and you keep the lever to stop any of them.
© 2026 Intramedial. All rights reserved. Intramedial is a product by Trustvice. Secured and supercharged by Avonao Labs.
Report abuseEach list covers one subject. Pick the few that match your work rather than one stream that covers everything.
For developers and teams who build on Intramedial or are deciding whether to.
What changed in the tools, the API, the SDKs and the data regions, so an integration never meets a change by surprise.
New tools, new capabilities and major changes, explained once they are live.
Related page
No spam
/toolsEvery entry we add to the changelog, as it is published.
Related page/changelogNew endpoints, deprecations and SDK releases that affect your integration.
Related page/docsWhen a data region opens, or when what a region stores changes.
Related page/regionsFor security, compliance, legal and procurement teams, and anyone who verifies receipts.
The notices you may be owed or need to act on: security advisories, changes to the published signing keys, incidents, sub-processor changes and changes to the legal documents.
Advisories about the service, the verifiers and the SDKs, with what to do.
Related page/securityWhen a key is added to or removed from the published key set.
Related page/docs/signing-keysFor anyone curious about evidence, receipts and record-keeping.
New blog posts, new cookbook recipes and notes on record-keeping rules, when they change.
New posts on evidence, ledgers and how we build Intramedial.
Related page/blogNew recipes: short, copyable integrations for one job each.
Related page/cookbookFor teams who came for one job and want news about that job only.
One list per solution page: what is new for that use case, from new tools to new guides.
Recording what AI agents did, with receipts others can check.
Related page/solutions/ai-agent-accountabilityLogs and evidence for the AI Act's record-keeping duties.
Related page/solutions/eu-ai-act-record-keepingFor shareholders, prospective investors and analysts.
Company announcements, new reports and governance documents, and the dates of investor events, as /investors publishes them.
Announcements and letters to shareholders, when we publish them.
Related page/investorsEach new report, statement or governance document on /investors.
Related page/investors#libraryFor anyone waiting for a page or programme we have announced but not opened yet.
Each waitlist sends one kind of email: the news that the page is open. Join as many as you like.
When we publish the first customer stories.
Related page/customersWhen we open our first roles.
Related page/careersStart from a bundle for your role, or tick lists one by one. You can choose up to twelve lists in one go and add more later from the manage page.
A bundle only ticks lists for you. Untick any of them, or add others, before you subscribe.
Nobody can sign your address up for anything. A list starts only when the owner of the inbox confirms it.
/newsletters/confirm?e=…&t=…&iat=…&s=…POST /api/subscriptions/confirmMany mail systems open every link in an email to check it for malware. If opening the link were enough, a scanner could confirm a list you never wanted, or end one you did. So confirming and unsubscribing always take a button press on the page.
The link carries your address, the lists and the time it was issued, signed by our server. The page cannot be used to confirm a different address or extra lists, and an old link stops working.
Ignore the email. Without the button press, your address is not added to any list.
These follow from how the emails are built and sent, not from a setting someone can quietly change.
We do not sell your address or share it with anyone for their own use. The providers who deliver email for us are listed on the sub-processors page.
Our emails contain no invisible images that report when you open them, and links go straight to their pages with no tracking redirect.
We never add your address to a list you did not confirm yourself, from the email we sent to that address.
We do not promise a schedule, so there is never an email written to fill a slot. A list emails when its subject has news.
Service notices are separate. If you have an account, we still send the service notices the terms require, such as security and billing notices. Those are not lists and do not depend on this page.
Leaving a list takes one button press and no sign-in. When you unsubscribe, the record of that subscription is deleted.
Every list email carries an unsubscribe link for that list. It opens a page with one button.
How unsubscribing works →02Ask for a manage link, and from it see every list your address receives, add lists or leave all of them at once.
Open the manage page →03Write to us and we will remove your address from every list. The privacy rights in the privacy policy apply in full.
Contact privacy →Several lists have a source you can follow without giving us an address.
Every blog post, newest first, with the full text, in any feed reader.
/blog/rss.xmlEvery changelog entry as RSS.
/changelog/rss.xmlCurrent service status, incidents and planned maintenance.
/statusHow we handle security, and how to report a vulnerability.
/securityWe keep only what a list needs to reach you, for as long as you stay subscribed.
Your consent: you give it by ticking the box and pressing Confirm, and you withdraw it by unsubscribing. Withdrawing does not affect anything sent before.
Cloudflare hosts the site, sends our email and runs the bot check on the form; Resend is the email fallback. Both are on the sub-processors page.
Product updates and security advisories, nothing else. You will get one email to confirm.
Already subscribed? Manage your lists →
Incidents and planned maintenance from the status page.
Notice of new or replaced sub-processors, as the DPA describes.
Related page/legal/subprocessorsChanges to the terms, the privacy policy and the other legal documents.
Related page/legalWhat changes in record-keeping rules mean for evidence, when they change.
Evidence of what was delivered, shown, accepted or sent.
Commits, builds, SBOMs and releases with a dated record.
Related page/solutions/software-supply-chainSigned availability records for SLAs and service credits.
Related page/solutions/uptime-sla-evidenceProof of what was delivered to an endpoint, and when.
Related page/solutions/webhook-delivery-proofWatching DNS records for changes.
Related page/solutions/domain-and-certificate-integrityRecords of consent, terms acceptance and privacy requests.
Related page/solutions/consent-and-privacy-recordsDates of shareholder meetings and investor updates, before each one.
When the partner programme opens for applications.
When the referral programme launches.
Related page/referralsWhen the startup programme opens.
Related page/programs/startupsWhen nonprofit and education terms are available.
Related page/programs/nonprofitsWhen the public roadmap goes live, and when it changes.
Related page/roadmapWhen security documents are available on request.
Related page/trust/documentsWhen our accessibility conformance report is published.
Related page/accessibility/conformance