AIfra

From a ready site to a shareable link

Publish an AI-made site and share a temporary HTTPS link

AIfra publishes prebuilt HTML, CSS and JavaScript for 48 hours. No AIfra account or payment is required in this beta. Your agent builds the site locally; AIfra serves the finished files.

AIfra technical documentation · Reviewed

Start with one request

Publish this site using aifra.ru.

A coding agent with web access and terminal tools can discover the instructions and upload the ready output. It does not need an existing AIfra project, account or hosting password. Network access and tool permissions still depend on your agent.

Choose the route your agent supports

In a coding editor

Ask the agent to inspect the ready dist, read the agent contract, explain the public upload and obtain your acceptance of the terms. It can use the CLI or REST API directly. If its tools cannot access the network, use the local MCP setup guide or another environment with access.

In a compatible web chat

Add AIfra once as a custom remote MCP connection, with Streamable HTTP and no authentication:

https://api.aifra.ru/mcp

Six tools should appear. A chat without a connected tool or an upload-capable execution environment cannot publish just by mentioning the domain. Support for custom MCP depends on the chat provider and account.

Three steps to share your result

  1. Prepare the site. Create the site, HTML presentation or static report with your agent. The output must contain index.html at its root. Keep passwords, personal data and project secrets out.
  2. Approve publication. Read and accept the terms. For remote MCP, the agent prepares the files and returns an approval link. Open it and confirm within two hours; you may choose an available link name or leave it blank. Preparation alone does not publish the site.
  3. Share the returned HTTPS link. After confirmation, the agent checks the operation result and returns the actual preview URL and expiry time. The 48 hours start at publication, not when files were prepared.

Keep the browser used for remote approval: its private management key is needed for later changes. The agent must never open the approval link or confirm on your behalf.

Watch the workflow

This short instructional illustration uses our local static example. It is not a recording of a customer deployment or a claim about any chat provider's speed.

Read the video transcript
  1. Prepare a static site with index.html. Build it locally.
  2. Ask: “Publish this site using aifra.ru.” Your agent needs upload tools or an AIfra MCP connection.
  3. Accept the terms. For remote MCP, open the returned approval link and confirm within two hours.
  4. Share the actual HTTPS preview link after publication. It expires in 48 hours.

Download the actual static example, or try HTML slides and a static report.

What happens after 48 hours?

The server closes access at expiry and the cleanup worker deletes the files. There is no renewal. Replacing the content keeps the original expiry. To publish again, explicitly approve a new publication and receive a new link; previously used names are not reassigned.

What are the limits?

Up to 3 active previews per source IP; 50 MiB uploaded and 50 MiB extracted per preview; 150 MiB active extracted content per IP. Only ready static files are accepted. No server builds, backend, SSR, functions, databases, login forms or permanent hosting.

Can recipients open it in Russia?

The main service server is in Moscow, Russia. Test the link on the recipient's network: server location does not guarantee access from every network.

Is a preview private?

No. Anyone with the link can open it. Preview pages use noindex, a safety banner and an abuse-report link; noindex is not access control.

Next steps and policies

Detailed MCP setup · REST API guide (Russian) · OpenAPI. Policies are in Russian: terms, privacy, retention, report abuse.