For teams considering adoption

Start with a real workflow. Prove the value before committing.

Our first priority is helping developers determine whether Andamento fits their application. Licensing should make evaluation practical—not force a company into a large commitment before it has tested the technology.

A low-friction path

From technical exploration to a commercial decision.

Begin with a real evaluation, consider a defined pilot when it makes sense, and discuss deployment terms only after you understand the SDK’s fit. Each stage below explains what is available today and what is still being considered.

01EXPLORE · CURRENT EVALUATION

Developer evaluation

90 days SDK evaluation period

Register, verify your email, and request access through the Developer Portal. Build a representative Apple-app workflow before making a licensing decision.

Review public documentation and SDK examples.
Test confirmations, silence, interruptions, and callbacks.
Measure integration work and application fit.

Access is a separate step after registration, subject to the SDK evaluation agreement and applicable permissions. Production distribution rights are not implied.

See SDK access steps

02VALIDATE · PROPOSED NEXT STEP

Early-adopter pilot

Scoped terms discussed individually

For a promising prototype, explore a time-bounded pilot with clearly stated objectives and permissions.

Agree on one real use case and success criteria.
Discuss duration, support scope, and milestones.
Define any production or distribution rights explicitly.

Pilot availability, pricing, and terms are not yet standardized or guaranteed.

Discuss a pilot

03DEPLOY · COMMERCIAL DIRECTION

Production licensing

Tailored no public rate established

Our working preference is predictable application-based licensing, with custom scope for broader enterprise deployments.

Agree on licensed application and deployment scope.
Define updates, maintenance, and support expectations.
Address multi-app or enterprise needs individually.

No published prices, MAU fees, support SLAs, escrow arrangements, or commercial rights are established by this page.

Contact SpeechTiles

Before your first prototype

What happens after you decide to evaluate?

The Developer Portal handles account registration, email verification, SDK access requests, agreement acceptance, and downloads. You can access it from the links below.

Create a developer accountRegister with an email address you can verify, then open the verification link sent to that address.
Request SDK evaluation accessSign in, complete the SDK-access request and applicable evaluation agreement. Creating an account alone does not grant an SDK download.
Receive access and downloadWhen access is granted, download the available SDK package through the portal and follow its integration guidance. We do not promise immediate approval or a fixed processing time.
Build and measure one real workflowTest the conversation on your target Apple hardware and compare the effort and experience with your other options.

A practical expectation

Public documentation is available without SDK access. To evaluate the SDK, register and request access through the Developer Portal.

Why we favor this approach

Make adoption easy to assess—and buying easy to explain.

For developers

Prototype before a purchasing decision

Engineers can determine whether the capabilities match the app's real conversational needs before asking for an organization-wide commitment.

For product teams

Budget for a defined deployment

Our working preference is predictable application-based commercial licensing rather than billing every spoken word or measuring every conversational turn.

For enterprise buyers

Negotiate what matters at scale

Multi-application scope, maintenance, support arrangements, and continuity requirements can be considered as part of a larger agreement.

For everyone

Evaluate engineering savings with evidence

Compare a real integration against building the equivalent layer using your team's alternatives. Don't rely on invented “three months saved” estimates.

A practical first evaluation

What would a useful pilot prove?

One meaningful workflow

Choose something involving multiple turns, confirmation, silence handling, or corrections—not just dictation.

One engineering comparison

Record SDK integration work, custom logic avoided, and the effort your alternative stack would require.

One experience review

Test interruptions, user mistakes, timing, application updates, and the overall experience on the target device.

SDK access currently requires developer registration and a separate SDK-access request. Downloads are provided through the Developer Portal when access is granted, subject to the applicable agreement.

Make the build-versus-buy decision measurable

Compare a representative workflow, not a hypothetical three-month estimate.

A practical evaluation can be small. Keep the requirements identical across approaches, and track the work that matters to your team.

Integration effort

Developer time to connect speech, runtime behavior, and application callbacks.

Interaction coverage

Confirmations, corrections, interruptions, silence, and unexpected responses.

Quality on device

Responsiveness and usability on actual target hardware and configured speech services.

Maintenance outlook

Custom code ownership, SDK upgrade effort, testing, and support requirements.

Existing AI voice platforms and other SDKs belong in this comparison when they are credible alternatives. A successful pilot does not establish universal savings or production suitability.

See what a team would otherwise build

Straight answers

Licensing questions we expect

Can I evaluate the SDK before paying for a commercial license?

The current developer access flow supports a time-limited SDK evaluation. Register and request access through the developer portal; the specific evaluation rights are governed by the current agreement.

Is there a published price per app, user, or developer?

There is no published standard price per app, user, or developer. We are evaluating an application-based licensing approach; commercial scope, pricing, and terms are discussed individually.

Can I launch a commercial app during evaluation?

Do not assume so. Production or distribution rights must be explicitly granted by the applicable license or separately negotiated pilot agreement.

Does the SDK require a connection to SpeechTiles for every conversation?

No. Conversation execution runs on-device. Licensing permissions are a separate mechanism with locally cached permissions; speech recognition and application services can have their own network dependencies.

What if my app serves multiple businesses or uses multiple bundle IDs?

Licensing for white-label applications, multiple bundle IDs, or application families is reviewed individually as part of defining commercial scope. No standard policy for these cases is currently published.

NEXT STEPS

Explore the SDK. Test your own workflow.

Review the public documentation, register for developer access, or tell us about the conversation your application needs.

Create developer account Read the API documentation Discuss an evaluation