Skip to content
Smriti AI

Google Cloud & Gemini

From business knowledge to coordinated action.

Cloud foundation

We build agentic products and enterprise platforms on Google Cloud, combining Gemini capabilities, Gemini Enterprise integrations, Google ADK and speech technologies with Smriti's own application engineering.

A concept screen. A procurement lead asks which vendor contracts renew this quarter. The answer cites three approved sources. Three coordinated agents show their completed steps, and a proposed action — sending two price-review requests — waits for the procurement lead to approve, edit or send it back.

DrawingAgent workspace on Google Cloud
TypeConcept interface
NoteNot a deployed product

Where the work is

Gemini provides model capabilities. Smriti engineers how those capabilities become a product.

A capable model is the beginning of a product, not the product. Organisations need agents that work with their own knowledge, act in their own systems and involve a person when a decision needs one.

Our work is everything in between: the interface people use, the orchestration of specialised agents, the connections to approved knowledge and business systems, and the evaluation and deployment that make the whole dependable.

What we engineer on Google Cloud

  • Product and interface design

    The experience people actually use, including review and approval steps.
  • Agent orchestration

    How specialised agents divide work, share context and hand off, built with ADK where it fits.
  • Business integrations

    Connections to the organisation's systems and knowledge, scoped to what each user may access.
  • Evaluation and deployment

    Task-level evaluation before release and the operational engineering to run the system.

Responsibility map

Who provides what in a Google Cloud project.

Google's technologies and our engineering do different jobs. Naming each one precisely keeps the boundary clear — for the organisation and for us.

Smriti engineers

The product people use, and what makes it dependable

  • Interfaces and product logic
  • AI harnesses
  • Agent orchestration
  • Business integrations
  • Evaluation and deployment

Google Cloud provides

Google's technologies, which we build with

  • Gemini Enterprise

    Role: Experiences and integrations

    In our projects: Google's intranet search, AI assistant and agent platform for organisations. We connect it to company systems and build agents for it where a project uses it.

    Keep in mind: Not a model-training or tuning service.

  • Gemini models

    Role: Model capabilities

    In our projects: Understanding, reasoning and generation, with the model chosen against the task.

    Keep in mind: We name a specific model version only when a project actually uses it.

  • Gemini Enterprise Agent Platform Formerly Vertex AI

    Role: Model access, tuning, agent hosting

    In our projects: Where a project uses it: access to models, tuning for supported Gemini models, and Agent Runtime for hosting agents.

    Keep in mind: Supervised tuning is available for specific Gemini models only — not every model, method or region.

  • Agent Development Kit (ADK)

    Role: Agent development and orchestration

    In our projects: The open-source framework we use to build, debug and deploy agents and the way they coordinate.

    Keep in mind: Not Gemini-only: model-agnostic, and deployable to Agent Runtime, Cloud Run, GKE or other infrastructure.

  • Cloud Speech-to-Text and Cloud Text-to-Speech

    Role: Voice interaction

    In our projects: Speech recognition and synthesis where an application needs a voice interface.

    Keep in mind: Voices, languages and models are confirmed for each application, not assumed.

The organisation's approved knowledge and systems

Documents, records and business tools — integrated with permission

DrawingResponsibility map — Google Cloud
TypeReference architecture
PracticeGoogle Cloud & Gemini

Model adaptation

We adapt a model only when the task requires it.

Many tasks can be met with clearer instructions, the right context, retrieval from approved knowledge and a well-built harness. We evaluate each step against the task before considering the next.

When evaluation shows a model does need adapting, we check what the selected model supports. Supervised tuning is available for specific Gemini models only — some in preview or in limited regions — so it is confirmed per project, never assumed.

  1. 01

    Instructions and context

    A clear task definition and the right context in every request.

    Evaluate against the task — stop here if it is met

  2. 02

    Retrieval from approved knowledge

    Answers grounded in the organisation's own sources rather than the model's general knowledge.

    Evaluate against the task — stop here if it is met

  3. 03

    Harness rules and tools

    Workflow rules, tool calls and checks around the model.

    Evaluate against the task — stop here if it is met

  4. 04

    Model adaptation

    Only if needed

    Supervised tuning, only when evaluation shows the earlier steps fall short and the selected Gemini model supports it.

DrawingOrder of adaptation
TypeProcess
PracticeGoogle Cloud

What we build

Agents that work with what an organisation already knows.

  • Answering questions from approved internal knowledge, with sources
  • Coordinating specialised agents across a multi-step business task
  • Preparing work for human review instead of acting unilaterally
  • Bringing agent capabilities into the tools a team already uses

Capability overview

Gemini-powered enterprise agents

Agents that work with an organisation's own knowledge and software, built on Google Cloud with Gemini models, Gemini Enterprise and the Agent Development Kit.

A capability overview describes what we engineer in this kind of project. It is not a case study: it names no customers and claims no results.

Google Cloud & Gemini

Have knowledge that should lead to action?

Tell us about the task, the knowledge it depends on and the systems it should act in. We will start with what the system must do — not with a model.