Skip to content

For organizations running Microsoft Intune

Our products

Avyna builds on the Microsoft estate you already run rather than replacing it.

  • Available now

    Avyna Catalog

    Self-service software and access for Microsoft Intune

    • Approval and delivery are the same event
    • The chain is yours to shape, then it maintains itself
    • Everyone gets their own catalog
    Start setup
    Explore Avyna Catalog
  • In pilot

    Avyna Core

    Device and user management for Microsoft Intune

    • Every Intune action, its own permission
    • Delegation that covers what, as well as who
    • An agent for what Intune does not hold
    Join the pilot
    Explore Avyna Core
Microsoft verified publisherCard details never reach our servers. Stripe takes payment
How access is granted

Built on what you already run

  • Microsoft Intune
  • Microsoft Entra ID
  • Microsoft 365
  • Nothing is migrated. Microsoft stays the system of record for identity and enrollment.

Avyna Catalog

The next four sections are about this product alone: what changes, how you start, what you are asked to approve, and what it costs.

Here for Avyna Core? It is in pilot, and has a page of its own.

Explore Avyna Core

Catalog What actually changes

Three things that are true and you can check each one.

Each one is visible in the product, and each is set against what an organization does today without it.

Approval and delivery are the same event

The final approval adds the requester, or the device they chose, to the group that grants the software. Nobody is in the loop afterwards, because there is nothing left to do.

Instead of a tool that routes the request and records the yes, while somebody still opens Intune and grants the access by hand.

There are no approver lists to maintain

Manager steps are resolved from your Microsoft directory as each step becomes the current one, then recorded on that step. A reorganization changes who approves what for every step not yet reached, and nobody edits anything.

Instead of approver lists that start going stale the day you finish configuring them.

Everyone gets their own catalog

Visibility is set per item, to named people or directory groups. Someone browsing sees what they are eligible for and nothing else.

Instead of advertising your whole estate to your whole company and declining most of what gets asked for.

Catalog Getting started

A consent, a plan, and you are working.

There is no implementation phase between buying and using. Signing up takes about a minute, in four steps: your organization and the agreements, a plan, Microsoft’s consent, then payment. Nothing is migrated, no second directory is created, and Microsoft stays the system of record. What you publish, and who approves it, takes as long as your own decisions take.

  1. 01

    Set up your organization

    Sign in, confirm your company details and accept the agreements, then choose a plan. Most of it is already filled in.

    Payment comes last, on Stripe’s hosted checkout. No card number is typed on an Avyna page.

  2. 02

    A Global Administrator grants consent

    On Microsoft’s own admin consent page, against a permission list Microsoft displays, for an application published by a Microsoft verified publisher. Every permission is explained in plain language before you get there.

    No password. No service account. No secret to email.

  3. 03

    Publish what people can ask for

    Publish the applications and groups people should be able to ask for, and set who approves what.

  4. 04

    Your people get to work

    Staff request what they need and follow it through each step. Approvers get a queue and decide, and the final approval grants the access.

Catalog Before you connect anything

You are not asked to trust us.
You are asked to check.

Access to your tenant is granted on Microsoft’s own admin consent page, by your own Global Administrator, for an application published by a Microsoft verified publisher. The publisher status and the permission list on that screen come from Microsoft, not from us. Payment works the same way: card details are entered on Stripe’s page and never reach our servers.

Read how access and payment work
  • Microsoft verified publisher

    Access is granted on Microsoft’s own admin consent screen, by your own Global Administrator, against a permission list Microsoft displays. We never ask for a password.

  • Card details never reach our servers

    Payment is taken on Stripe’s hosted checkout. No card number, expiry or security code reaches our servers or database. We hold a reference to your Stripe record and nothing more.

  • Least privilege, stated up front

    Catalog lists every permission it requests, each with a plain sentence saying why, before you are sent to Microsoft. Nothing is granted through a form on our site.

Catalog Pricing

Same product, whatever the plan.

Plans differ by one thing: how many people in your organization can use Catalog. Self-serve, billed through Stripe.

Avyna Catalog

One product. Priced by how many people use it.

Plans differ by exactly one thing: how many people in your organization can use Catalog. There is no smaller version of the product and no feature held back for a higher plan.

From$254/month30 days free

Up to 200 Catalog users≈ $1.27 per user / month

  • Priced per organization against a Catalog-user limit — not per seat. The bill does not move every time someone joins.
  • A Catalog user is counted from their first sign-in. Disabled and removed accounts release their place automatically.
  • The limit is visible in the product before it bites: administrators are warned as usage approaches it and told when it is reached.
See Avyna Catalog plans

Prices exclude tax. Payment is taken on Stripe’s hosted checkout, and card details never reach our servers.

Prices are indicative, shown in your region's currency. Your organization's binding price and market are confirmed when you sign in.

Questions

Asked before anything is signed.

Who is Avyna?

Avyna by AlgoCreed builds management software for organizations running Microsoft 365 and Intune. It has two products: Avyna Catalog, available now, and Avyna Core, in pilot. Both ship in English and French.

How do we know you are who you say you are?

You do not have to take our word for it. Access to your tenant is granted on Microsoft’s own admin consent page, using a registered application, and Microsoft shows its verified publisher status there. Microsoft checks that status against its own records. We do not assert it.

Do we have to give you a Microsoft password?

No. There is no password to hand over, no service account to create and no secret to email. A Global Administrator approves an explicit permission list once, on a page we do not control.

Can we try it before paying?

Yes, for Avyna Catalog: 30 days free on any plan, and it is the whole product. A payment method is taken at sign-up on Stripe’s hosted checkout, and nothing is charged until the 30 days are up. Cancel before then and you pay nothing, even on a twelve-month commitment. Avyna Core has no trial: it is in pilot, so it starts with a conversation.

How long does setup take?

Signing up for Catalog takes about a minute, in four steps: confirm your organization’s details and the agreements (most of it is already filled in), choose a plan, have a Global Administrator grant consent, and add a payment method. What takes longer is your own decision about what to publish and who approves it.

Do we need to migrate anything?

No. Microsoft stays the system of record for identity and enrollment. Catalog reads from what you already run and acts through it.

Catalog has its own FAQ, with the questions asked before a purchase, grouped by topic. Read the Catalog FAQ

Company

Avyna by AlgoCreed. We build for the Microsoft estate.

Every organization on Microsoft 365 and Intune ends up doing the same handful of jobs by hand — chasing approvals, finding out what a machine really is, granting access one ticket at a time. We build software for those jobs, one product at a time, and we describe each one exactly as far as it goes.

How we work

Four things we decided early and kept.

Say what the product does, and what it does not

Every product page on this site carries a list of what that product cannot do. It is there because you will find out in a demo anyway, and finding out on week three is worse for both of us.

Hold as little as possible

Card details are entered on Stripe and never reach our servers. Microsoft stays the system of record for identity and enrollment. Catalog asks for six Microsoft permissions, five of them read-only.

Fit the organization, not the org chart Microsoft assumed

Roles you build yourself, scopes that match your actual territories, approval chains shaped per item. The product should bend to how you work rather than the other way round.

Write for people who read carefully

Our audience is technical and can tell the difference between a claim and a fact. So the copy names Microsoft concepts by their real names and leaves the adjectives out.

The short version

Everything factual on one card.

Useful for a procurement form. If something you need is not here, ask — we would rather answer than let you guess.

Brand
Avyna
Built by
AlgoCreed
Products
Avyna Catalog, Avyna Core
Languages
English and French
Billing currency
USD
Payments
Stripe
Publisher status
Microsoft verified publisher

Microsoft, Microsoft 365, Intune and Entra are trademarks of the Microsoft group of companies. “Microsoft verified publisher” refers to the status Microsoft displays on its own admin consent screen for our registered application. Avyna is not affiliated with, endorsed by or resold by Microsoft.

Catalog Available now

Put the catalog in front of your people.

Free for the first 30 days on every plan. Signing up takes about a minute, in four steps: your organization and the agreements, a plan, Microsoft’s consent, then payment.

Microsoft verified publisherCard details never reach our servers. Stripe takes payment